Timing system and method with integrated event participant tracking management services

ABSTRACT

An automated system and method for managing a tracking and an automated real-time remote reporting thereof of a participant&#39;s participation in an event having a participant event management system (PEMS) that receives a request for tracking of the participant, a participant proximity detector detects the proximity of the participant to a detection point, a location detection system receiving and transmitting participant location data, the timing system receives the preorder request from the PEMS, determines a time of passing of the detection point of the participant, receives the location data and associates the participant event number with the participant identifier number, and transmits the location data forming at least a part of the participant tracking data to an output interface.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation application of PCT InternationalApplication No. PCT/US13/23167 filed on Jan. 25, 2012, which claimed thebenefit of U.S. Provisional Application No. 61/590,782, filed on Jan.25, 2012.

Further, for US applications, this application is a continuation in partapplication that claims priority to the following applications:

-   -   1. United States national phase 35 USC §371 application Ser. No.        13/528,148, filed Aug. 31, 2012, which claimed priority to        PCT/US2011/26717, filed Mar. 1, 2011, which claims the benefit        of U.S. Provisional Application No. 61/309,259, filed on Mar. 1,        2010 entitled VARIABLY SPACED MULTI-POINT RFID TAG READER        SYSTEMS AND METHODS; and U.S. Provisional Application No.        61/369,013, filed on Jul. 29, 2010, entitled AUTOMATED TIMING        SYSTEMS AND METHODS HAVING MULTIPLE TIME EVENT RECORDERS AND AN        INTEGRATED USER TIME ENTRY INTERFACE.    -   2. United States national phase 35 USC §371 application Ser. No.        13/521,700, filed Jul. 11, 2012, which claimed priority to        PCT/US2011/20901, filed Jan. 11, 2011, which claims the benefit        of U.S. Provisional Application No. 61/294,024, filed on Jan.        11, 2010, entitled RFID SPORTS TIMING COMMUNICATIONS SYSTEMS AND        METHODS; and U.S. Provisional Application No. 61/369,013, filed        on Jul. 29, 2010, AUTOMATED TIMING SYSTEMS AND METHODS HAVING        MULTIPLE TIME EVENT RECORDERS AND AN INTEGRATED USER TIME ENTRY        INTERFACE.    -   3. U.S. application Ser. No. 13/194,880, filed Jul. 29, 2011,        and PCT/US11/46032, filed Jul. 29, 2011, each of which claims        the benefit of U.S. Provisional Application No. 61/369,013,        filed on Jul. 29, 2010, entitled AUTOMATED TIMING SYSTEMS AND        METHODS HAVING MULTIPLE TIME EVENT RECORDERS AND AN INTEGRATED        USER TIME ENTRY INTERFACE.    -   4. United States national phase 35 USC §371 application Ser. No.        13/980,539, filed Jul. 18, 2013 that claimed priority to        PCT/US12/22125, filed Jan. 20, 2012, which claims the benefit of        U.S. Provisional Application No. 61/434,769, filed on Jan. 20,        2011 entitled SYSTEMS AND METHODS FOR IMAGE CAPTURE INTEGRATION        AND DETECTION POINT LASER DETECTION IN AN EVENT TIMING SYSTEM.    -   5. United States national phase 35 USC §371 application Ser. No.        13/980,675, filed Sep. 11, 2013 that claimed priority to        PCT/US12/022126, filed Jan. 20, 2012, which claims the benefit        U.S. Provisional Application No. 61/434,769, filed on Jan. 20,        2011 entitled SYSTEMS AND METHODS FOR IMAGE CAPTURE INTEGRATION        AND DETECTION POINT LASER DETECTION IN AN EVENT TIMING SYSTEM.    -   6. United States national phase 35 USC §371 application Ser. No.        13/980,545, filed Jul. 18, 2013 that claimed priority to        PCT/US12/022132, filed Jan. 20, 2012, which claims the benefit        of U.S. Provisional Application No. 61/434,782, filed on Jan.        20, 2011 entitled EVENT PARTICIPANT LOCATION TRACKING DEVICE AND        TIMING SYSTEM AND METHOD.

The disclosures of the above applications are incorporated herein byreference.

FIELD

The present disclosure relates to event registration and timing systemsand, more specifically, to integrated timing system ITS integrating atiming system TS with an event participant registration and preorderingsystem (PEMS) for event services for the participant.

BACKGROUND

The statements in this section merely provide background informationrelated to the present disclosure and may not constitute prior art.

SUMMARY

The inventor hereof has succeeded at designing an integrated timingsystem having an integrated participant event management and servicessystem including the pre-purchase and management of participant eventimage capture services.

In a first aspect, an automated system and method for managing aparticipant's participation in an event having a participant eventmanagement system (PEMS), a participant proximity detector, an imagecapture system and a timing system. The participant event managementsystem (PEMS) receives a request for capturing an image of theparticipant during the event. The participant proximity detector detectsthe proximity of the participant to a detection point and receives theparticipant number. The image capture system receives an instruction forcapturing an image of the participant, receives an indication that theparticipant has been detected, and captures an image of the participant.The timing system receives the preorder request from the PEMS,determines a time of passing of the detection point of the participant,associates the participant event number with the participant identifiernumber, generates the instruction for capturing the image of theparticipant, and receives the transmitted captured image.

According to one aspect, an automated system is provided for managing aparticipant's participation in an event wherein the participant istracked using a participant identifier having a unique participantnumber. The system includes a participant event management system(PEMS), a participant proximity detector, an image capture system and atiming system. The participant event management system (PEMS) has a userinterface receiving an input from the participant including participantdata and a registration of the participant in the timed event, the PEMSassigning the participant a participant event number responsive thereto,the PEMS also receiving a preorder request for capturing an image of theparticipant during the event, the PEMS having a communication interfacetransmitting the assigned participant event number and the preorderrequest. The participant proximity detector detecting the participantwhen in proximity to the participant proximity detector at a detectionpoint during the event and receiving the participant number from theparticipant identifier, identifying a read time of the receivedparticipant identifier read, and transmitting the participant identifiernumber and the identified participant identifier read time over a datainterface. The image capture system has one or more image capturedevices and a data interface receiving an instruction for capturing animage of the participant associated with the participant identifiernumber, receives an indication that the participant proximity detectorhas received the participant identifier read of the participantidentifier number of the participant, captures at least one image of theparticipant when the participant identifier of the participant is inproximity to the participant proximity detector responsive to thereceived instruction and the received indication of the proximity of theparticipant's identifier, generates an image capture message includingthe captured image, and transmits the image capture message over thedata interface. The timing system has a data communication interface, amemory and computer executable instructions, the timing system receivingthe participant identifier number and the participant identifier readtime from the participant proximity detector, receives the transmittedportion of the assigned participant event number and the preorderrequest from the PEMS, determines a time of passing of the detectionpoint of the participant responsive to the received participantidentifier number and participant identifier read time, associates theparticipant event number with the participant identifier number andgenerating the instruction for capturing the image of the participant,receives the transmitted image capture message from the image capturesystem, and stores in the memory the determined time of passing and theimage of the image capture message in the memory associated with theassigned participant event number.

According to another aspect, an automated system is provided formanaging a participant's participation in an event wherein theparticipant is tracked using a participant identifier having a uniqueparticipant identifier number. The system includes a participant eventmanagement system (PEMS), a participant proximity detector, and an imagecapture system and a timing system. The participant event managementsystem (PEMS) including a user interface receives an input from theparticipant including participant data and a registration of theparticipant in the event, the PEMS assigning the participant aparticipant event number responsive thereto, the PEMS also receives apreorder request for capturing an image of the participant during theevent, the PEMS having a communication interface transmitting at least aportion of the received participant data, the assigned participant eventnumber and the preorder request. The participant proximity detectorhaving a processor, a memory, a clock, an participant transceiver withan antenna receiving the participant identifier number from theparticipant identifier when the participant identifier comes within aproximity of the participant proximity detector when placed at adetection point of the event, identifying from the clock a read time ofthe received participant identifier read, and a data interface fortransmitting the participant identifier number and the identifiedparticipant identifier read time. The image capture system has an imagecapture device and a data interface receiving an instruction forcapturing an image of the participant associated with the participantidentifier number, receiving an indication that the participantproximity detector has received the participant identifier read of theparticipant identifier number of the participant, and capturing at leastone image of the participant when the participant identifier of theparticipant is in proximity to the participant proximity detectorresponsive to the received indication, generating an image capturemessage including the image, and transmitting the image capture messageover the data interface. The timing system has a data communicationinterface, a memory and computer executable instructions, the timingsystem receiving the participant identifier number and the participantidentifier read time from the participant proximity detector, receivingtransmitted portion of the participant data, the assigned participantevent number and the preorder request from the PEMS, thereafterassociating the participant event number with the participant identifiernumber and generating the instruction for capturing the image of theparticipant, receiving the image capture message from the image capturesystem, determining a time of passing of the detection point of theparticipant responsive to the received participant identifier number andparticipant identifier read time, and storing in the memory thedetermined time of passing and the image of the image capture message inthe memory.

According to yet another aspect, an automated system provides formanaging a participant's participation in an event wherein theparticipant is tracked using a participant identifier having a uniqueparticipant identifier number. The system includes a participant eventmanagement system (PEMS), a participant proximity detector, a locationdetection device an image capture system and a timing system. Theparticipant event management system (PEMS) includes a user interfacereceiving an input from the participant including participant data and aregistration of the participant in the event, the PEMS assigning theparticipant a participant event number responsive thereto, the PEMS alsoreceiving a preorder request for tracking of the participant during theevent, the PEMS having a communication interface transmitting theassigned participant event number and the preorder request. Theparticipant proximity detector having a processor, a memory, a clock, anRFID transceiver receiving the participant identifier number from theparticipant identifier when the participant identifier comes within aproximity of the participant proximity detector when placed at adetection point of the event, identifying from the clock a read time ofthe received participant identifier read, and a data interface fortransmitting the participant identifier number and the identifiedparticipant identifier read time. The location device associated withthe participant identifier of the participant, the location devicehaving a location data receiver for receiving location data from alocation providing source, and a wireless communication interface, thelocation detection device receiving location information from thelocation providing source, time stamping each received locationinformation, and transmitting participant location data over thewireless interface. The location detection device in at least periodicwireless communication with the location device for receiving thetransmitted participant location data, and transmitting the receivedlocation data to the timing system. The timing system has a datacommunication interface, a memory and computer executable instructions,the timing system receiving the participant identifier number and theparticipant identifier read time from the participant proximitydetector, and receiving the location data, the timing system determininga time of passing of the detection point of the participant responsiveto the received participant identifier number and participant identifierread time, storing the determined time of passing and the receivedlocation data in the memory associated with the participant identifiernumber of the participant, receiving the transmitted assignedparticipant event number and the preorder request from the PEMS,associating the participant event number with the participant identifiernumber and transmitting the received location data to an outputinterface.

According to still another aspect, an automated method provides formanaging a participant's participation in an event wherein theparticipant is tracked using a participant identifier having a uniqueparticipant identifier number. The method includes various stepsperformed by various defined components. These include a) in aparticipant event management system (PEMS) having a user interface,

receiving an input from the participant including participant data and aregistration of the participant in the event, assigning the participanta participant event number responsive thereto, receiving a preorderrequest for capturing an image of the participant during the event, andtransmitting the assigned participant event number and the preorderrequest;b) in a participant proximity detector, detecting the participantidentifier when in proximity to the participant proximity detector at adetection point during the event, receiving the participant identifiernumber from the participant identifier, identifying a read time of thereceived participant identifier read, and transmitting the participantidentifier number and the identified participant identifier read timeover a data interface;c) in an image capture system with an image capture device and a datainterface, receiving an instruction for capturing an image of theparticipant associated with the participant identifier number, receivingan indication that the participant proximity detector has received theparticipant identifier read of the participant identifier number of theparticipant, capturing at least one image of the participant when theparticipant identifier of the participant is in proximity to theparticipant proximity detector responsive to the received indication,generating an image capture message including the image, andtransmitting the image capture message over the data interface; and d)in a timing system having a processor, a data communication interface, amemory and computer executable instructions for receiving theparticipant identifier number and the participant identifier read timefrom the participant proximity detector, receiving the image capturemessage from the image capture system, determining a time of passing ofthe detection point of the participant responsive to the receivedparticipant identifier number and participant identifier read time,storing the determined time of passing and the image of the imagecapture message in the memory, receiving the assigned participant eventnumber and the preorder request from the PEMS, associating theparticipant event number with the participant identifier number, andgenerating the instruction for capturing the image of the participant.

In yet an aspect, an automated method is provided for managing aparticipant's participation in an event wherein the participant istracked using a participant identifier having a unique participantidentifier number. The method is performed in defined system componentsincluding: a) in a participant event management system (PEMS) includinga user interface, receiving an input from the participant includingparticipant data and a registration of the participant in the event,assigning the participant a participant event number responsive thereto,receiving a preorder request for tracking of the participant during theevent, and transmitting the assigned participant event number and thepreorder request; b) in a participant proximity detector having aprocessor, a memory, a clock, an participant transceiver, receiving theparticipant identifier number from the participant identifier when theparticipant identifier comes within a proximity of the participantproximity detector when placed at a detection point of the event,identifying a read time of the received participant identifier read, andtransmitting the participant identifier number and the identifiedparticipant identifier read time; c) in a location device associatedwith the participant identifier of the participant, receiving locationdata from a location-providing source, time stamping each receivedlocation information, and transmitting participant location data overthe wireless interface; d) in a location detection device in at leastperiodic wireless communication with the location device, receiving thetransmitted participant location data, and transmitting the receivedlocation data to the timing system; and e) in a timing system having aprocessor, a data communication interface, a memory and computerexecutable instructions, receiving the participant identifier number andthe participant identifier read time from the participant proximitydetector, receiving the location data, determining a time of passing ofthe detection point of the participant responsive to the receivedparticipant identifier number and participant identifier read time,storing the determined time of passing and the received location data inthe memory associated with the participant identifier number of theparticipant, receiving the assigned participant event number and thepreorder request from the PEMS, associating the participant event numberwith the participant identifier number, and transmitting the receivedlocation data to an output interface.

Further aspects of the present disclosure will be in part apparent andin part pointed out below. It should be understood that various aspectsof the disclosure might be implemented individually or in combinationwith one another. It should also be understood that the detaileddescription and drawings, while indicating certain exemplaryembodiments, are intended for purposes of illustration only and shouldnot be construed as limiting the scope of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of a typical STS system configurationthat is used to read a Race Bib Tag as it passes participant proximitydetector reader that can include in some embodiments, antennas aremounted overhead and on the side of a racecourse. The specific locationof the antennas could be changed to include any position that is deemedsuitable for receiving the Bib Tag signal from the tag according to oneexemplary embodiment.

FIG. 2 is a schematic drawing showing an participant Timing System usingredundant participant proximity detector shown as an participantproximity detector system (TRS) each with multiple participant proximitydetector detection systems (DS) according to one exemplary embodiment,according to a first exemplary embodiment.

FIG. 3 is a block diagram showing the system architecture of a timingsystem (STS) with integrated participant identifier read triggeringand/or laser detection triggering for capturing and associating aphotograph or video according to one exemplary embodiment.

FIG. 4 is schematic illustrating the layout of an event coursepositioned image capture point having participant proximity detectorspositioned for triggering the capture and association of a photographimage or video of a passing participant according to one exemplaryembodiment.

FIG. 5 is schematic illustrating a second layout of a system for anevent course positioned at an image capture point having participantproximity detectors positioned for triggering the capture andassociation of a photograph images or videos of two or more passingparticipants according to one exemplary embodiment.

FIG. 6 is schematic illustrating a third layout of a course positionedimage capture point having participant proximity detectors and a laserdetection system, each positioned for triggering the capture andassociation of a photograph images or videos of passing participantsaccording to one exemplary embodiment.

FIG. 7 is schematic illustrating a third layout of a course positionedimage capture point having participant proximity detectors forparticipant identification and a laser detection system for triggeringthe capture and association of a photograph images or videos of passingparticipants according to one exemplary embodiment.

FIG. 8 is a block diagram flow chart illustrating a process forparticipant preordering of the capture and processing of eventphotographic images and/or video by a participant in an event accordingto one exemplary embodiment.

FIG. 9 is a user interface for a timing system TS for receiving userdata entries according to one exemplary embodiment.

FIG. 10 is a high-level architecture of an Integrated Timing System ITShaving a timing system TS with plurality of automated tag readingsystems and at least one PEMS system according to one exemplaryembodiment.

FIG. 11 is a schematic drawing showing the system architecture of thecommunication system suitable for use with one exemplary embodiment.

FIG. 12 is another high level architecture of an Integrated TimingSystem (ITS) having a plurality of automated tag reading systems and atleast one PEMS system according to one exemplary embodiment.

FIG. 13 is an illustration of the format for the variable length packetmessages according to one exemplary embodiment.

FIG. 14 is an illustration of the formats for an exemplary set ofmessages according to one exemplary embodiment.

FIG. 15 is a block diagram of a participant event management system PEMSused for registration and pre-ordering of participant event relatedservices according to one exemplary embodiment.

FIG. 16 is a second block diagram of a participant event managementsystem PEMS used for registration and pre-ordering of participant eventrelated services and the subsequent providing of those pre-ordered eventrelated services according to one exemplary embodiment.

FIG. 17 is a block diagram of a specialized ITS computer system that isalso suitable for implementing the object detection systems and timingsystems in various embodiments as described herein.

It should be understood that throughout the drawings, correspondingreference numerals indicate like or corresponding parts and features.

DETAILED DESCRIPTION

The following description is merely exemplary in nature and is notintended to limit the present disclosure or the disclosure'sapplications or uses.

Before turning to the figures and the various exemplary embodimentsillustrated therein, a detailed overview of various embodiments andaspects is provided for purposes of breadth of scope, context, clarity,and completeness.

In one embodiment, an automated system and method for managing aparticipant's participation in an event having a participant eventmanagement system (PEMS), a participant proximity detector, an imagecapture system and a timing system. The participant event managementsystem (PEMS) receives a request for capturing an image of theparticipant during the event. The participant proximity detector detectsthe proximity of the participant to a detection point and receives theparticipant number. The image capture system receives an instruction forcapturing an image of the participant, receives an indication that theparticipant has been detected, and captures an image of the participant.The timing system receives the preorder request from the PEMS,determines a time of passing of the detection point of the participant,associates the participant event number with the participant identifiernumber, generates the instruction for capturing the image of theparticipant, and receives the transmitted captured image.

In one embodiment, an automated system for managing a participant'sparticipation in an event wherein the participant is tracked using aparticipant identifier having a unique participant identifier number.This can be a participant tag or other participant identifier such as abib or other means including images of the participant or their vehiclefor uniquely identifying the particular participant from among aplurality of participants. Often these events are timed events, but thepresent disclosure includes both timed and untimed events wherein aparticipant in the event is tracked. It should be noted that theparticipant tag or other participant identifier and participant tagnumber can be of any type. As will be discussed herein, by way of oneexemplary embodiment, the participant identifiers can be participantidentifiers such as an RFID tag and the RFID detection systems and RFIDparticipant proximity detectors can then be RFID tag readers anddetection systems. However, RFID tags and tag readers are only onetechnology, and for the purposes of this disclosure, one skilled in theart should be aware that any types of RFID tags and readers or trackersor detection systems could be used and still be within the scope of thepresent invention. As such, for the remainder of the presentspecification and disclosure, any reference to an RFID tag or RFIDtechnology is only exemplary, and should not be viewed as being limitedto only RFID technology. Further, any reference herein to a tag readershould be understood to be any participant proximity detector thatdetects the presence of the participant in proximity to the detector.This could include an image or laser or GPS detection system andtechnology as well as the RFID technology, and other relatedtechnologies, and all are considered with the scope of this disclosure.Any reference to tag reader or tag should be interpreted as only oneexemplary embodiment for implementing the tracking and identification ofthe participant relative to a detector.

The timing system can include a participant event management system(PEMS) including a user interface receiving an input from theparticipant including participant data and a registration of theparticipant in the timed event, the PEMS assigning the participant aparticipant event number responsive thereto, the PEMS also receiving apreorder request for capturing an image of the participant during theevent, the PEMS having a communication interface transmitting at least aportion of the received participant data, the assigned participant eventnumber and the preorder request, an RFID tag reader detecting the RFIDtag when in proximity to the RFID tag reader at a detection point duringthe event and receiving the RFID tag number from the RFID tag,identifying a tag read time of the received RFID tag read, andtransmitting the RFID tag number and the identified RFID tag read timeover a data interface, an image capture system with an image capturedevice and a data interface receiving an instruction for capturing animage of the participant associated with the RFID tag number, receivingan indication that the RFID tag reader has received the RFID tag read ofthe RFID tag number of the participant, and capturing at least one imageof the participant when the RFID tag of the participant is in proximityto the RFID tag reader responsive to the received indication, generatingan image capture message including the image, and transmitting the imagecapture message over the data interface, and a timing system having aprocessor, a data communication interface, a memory and computerexecutable instructions, the timing system receiving the RFID tag numberand the RFID tag read time from the RFID tag reader, and receiving theimage capture message from the image capture system, the timing systemdetermining a time of passing of the detection point of the participantresponsive to the received RFID tag number and RFID tag read time,storing the determined time of passing and the image of the imagecapture message in the memory, the timing system also receiving theparticipant data, the assigned participant event number, and thepreorder request from the PEMS, thereafter associating the participantevent number with the RFID tag number and generating the instruction forcapturing the image of the participant.

In some embodiments, the preorder request includes a designation for thedelivery of the captured image, wherein the PEMS transmits the deliverydesignation and the timing system receiving the transmitted deliverydesignation, wherein the timing system is configured to transmit thereceived captured image over the data communication interface responsiveto the received delivery designation.

In some embodiment, the delivery designation is selected from the groupconsisting of: a web page, a web page of the PEMS, a mobile phone, anemail address, a text message, a social network wall, and an internetaddress.

In some embodiment, the preorder request includes a designation fordelivery of the captured image during or following the event, whereinsuch delivery designation includes one or more of the following:

a) updating the participant's social network wall with the capturedimage and/or determined time of passing,

b) updating a third parties social network wall with the captured imageand/or determined time of passing,

c) transmitting an email to an email address including the capturedimage and/or determined time of passing,

d) transmitting a text message to telephone number including thecaptured image and/or determined time of passing,

e) posting on a webpage the captured image and/or determined time ofpassing,

f) updating an application with the captured image and/or determinedtime of passing,

g) displaying on a coupled display the captured image and/or determinedtime of passing, and

h) updating a webpage or display or data file in the PEMS with thecaptured image and/or determined time of passing.

As such, the timing system and the PEMS system can work together forproviding a captured image (that includes a streaming of images such asa video) to various participant or third party designated output andbased on the format that is required capture images or video of theparticipants at any timing point and then associate the photo withmultiple tag or participant identifier reads that occurred at the sametime as there may be numerous participants at that location. Theidentified time comes from the timing system, which is synchronized tothe detector/reader time. Thus, the system can take a photo and or videoand determine based on the reads which participant is associated withthe images. As numerous participant proximity detections are made at anydetection point. This can also be helpful for backing up a participantdetection system that may miss a participant at a particular detectionpoint. Therefore, if a participant knows about when they crossed theparticular detection or timing point, an operator of the timing and/orPEMS system can retrieve the participant's captured image even thoughthe read did not so identify them.

In another embodiment, videos of the participants at any timing point ordetection point that is detected by a participant proximity detectorsuch as with an RFID chip read that triggers the recording of a video.In this case, since the participant can be identified prior to thedirect proximity to the image capture device, for example an RFID tagread that may be as much as 75 feet prior to the actual monitored point,the video image capture device can record images of the participant asthey approach a timing point or at other locations based on userdefinable parameters. This can include having a photo taken 20 to 50feet after the timing point because the captured image or picture maylook better. In this case, the process described herein for tag readsand image capture can include a time offset or delay so that the imagecapture is at the preferred operator or participant location rather thanat a participant detection point.

In some embodiments, the PEMS includes a payment receipt interface forreceiving a payment by the participant in response to the participantregistering for the event and/or submitting the preorder request forcapturing an image of the participant during the event. In someembodiment, the PEMS transmits a payment indicator reflecting saidpayment and identifying services associated with said received payment,and wherein the timing system receives the payment indicator for theparticipant and stores the payment indicator and identifies the servicesassociated with the payment in a data file associated with theparticipant, such as the bib number, participant number, or the RFID tagnumber.

In some embodiments, the image is encrypted and/or compressed andwherein the image is transmitted with an indicator of such encryption orcompression.

In some embodiments, the PEMS is receiving in the preorder request arequest for tracking of the participant during the event. The systemfurther includes a location device associated with the RFID tag of theparticipant, the location device having a location data receiver forreceiving location data from a location providing source, and a wirelesscommunication interface, the location detection device receivinglocation information from the location providing source, time stampingeach received location information, and transmitting tag location dataover the wireless interface, a location detection device in at leastperiodic wireless communication with the location device for receivingthe transmitted tag location data, and transmitting the receivedlocation data to the timing system, wherein the timing system receivesthe preorder request from the PEMS including the request for tracking ofthe participant and stores the received location data for theparticipant in a data file associated with the participant.

For example, the system as described herein can associate capturedphotos or videos taken anywhere on the route R where location data isavailable. If a participant has a GPS enable tracking device such as asmart phone or provided location tractor device, images capture devicescan be located at any location on a route R and not necessarilyassociated with a participant proximity detector such as an RFID tagreader at a split point or finish line. In this embodiment, the imagecapture devices such as cameras capture all video or take photosthroughout the entire event of all passing participants. These are allstored and have a GPS location and time of capture associated with each.As such, an operator or software system can then use location datacaptured from the participant's location tracking device to associatethe location of the participant at the various image capture devices(whose location is also known). In this manner, the captured locationdata of the participant can be compared with the captured imagesthroughout the traveled route.

In some embodiments, the preorder request includes a designation for thedelivery of the tracking data during or following the event, wherein thePEMS transmits the tracking delivery designation and the timing systemreceiving the transmitted tracking delivery designation, wherein thetiming system is configured to transmit the received tracking data overthe data communication interface responsive to the received trackingdelivery designation.

In some embodiments, the tracking delivery designation is selected fromthe group consisting of: a web page, a web page of the PEMS, a mobilephone, a wall of a social network, and an internet address.

In some embodiments, the preorder request includes a designation fordelivery of the tracking data of the participant during or following theevent, wherein such tracking delivery designation includes one or moreof the following:

a) updating the participant's social network wall with the tracking dataand/or determined time of passing,

b) updating a third parties social network wall with the tracking dataand/or determined time of passing

c) posting on a webpage the tracking data and/or determined time ofpassing

d) updating an application with the tracking data and/or determined timeof passing,

e) displaying on a coupled display a map showing the location based onthe tracking data for the participant, and

f) updating a webpage or display or data file in the PEMS with thecaptured image and/or determined time of passing.

In some embodiments, the PEMS system hosts a webpage including the userinterface.

As a couple of examples of such as system and services enabled by thissystem, a system can track a participant using GPS or other form oflocation tracking throughout the event. The timing system and or PEMScan post live captured image of the participant on a screen, display, orwebpage that displays a moving map of the route while the participanttravels from the beginning to the end. In this manner, throughout theentire event, relatives, fans, race organizers, media locally positionedor remote from the event can view the captured images of the particulardesired participant at any point during the event. In other words, as afriend is running the Boston Marathon, another friend can follow hisprogress on a smart phone or webpage by watching the displayed movingmap. As the participant passes a camera location, the photo or video istaken of him and the present system as described herein can provide forthe displaying of such captured images of that particular friendparticipant on a map that is generated, transmitted and then displayedon my desired device. The application of the user interface can includea capability enabling me to not only view the captured images in nearreal time, but can also enable the viewer to manipulate the images suchas to crop the image, to zoom in or out.

In another application and set of enabled services, the image capturedevices can send the images to the timing or PEMS or other system thatincludes facial recognition software. The facial recognition softwarecan be used to enable the identification of a participant. This can bethe sole means of participant detection or can be a supplementalparticipant proximity detection capability for identifying a participantwho may not have worn their bib properly during the race or whose RFIDtag chip went dead. In practice, in some embodiments, this may includethe capturing of an initial participant image as a part of theparticipant data during the PEMS registration process. For instance,when a participant provides the PEMS with participant data, this couldinclude capturing an image of the participant's face. This can beprovided by the Applicant or captured and provided via a smart phoneapplication for instance or via a webcam at home on their computer, orduring the day of the race at the location of the race. Now that thesystem has the participant's initial photo, the software can identifykey features such as their face, hair color, tattoos, and use thatinformation to later identify that person from among the plurality ofparticipants when a video or a photo is taken of the participant duringthe event. In the alternative, the image capture device and recognitionsoftware can be used to capture an image of a participant number such asa car number or bib number for participant identification and/orparticipant proximity detection. This can include reading a QR code, abar code, a car or bike number or the bib number itself and identify theparticipant from a comparison of the stored participant data.

In another embodiment, an automated system for managing a participant'sparticipation in a timed event wherein the participant is tracked usingan a participant identifier such as an RFID tag that has a unique RFIDtag number, the system comprising: a participant event management system(PEMS) including a user interface configured for receiving an input fromthe participant including participant data and a registration of theparticipant in the timed event, the PEMS assigning the participant aparticipant event number responsive thereto, the PEMS also configuredfor receiving a preorder request for capturing an image of theparticipant during the event, the PEMS having a communication interfaceconfigured for transmitting at least a portion of the receivedparticipant data, the assigned participant event number and the preorderrequest, an RFID tag reader having a processor, a memory, a clock, anRFID transceiver receiving the RFID tag number from the RFID tag whenthe RFID tag comes within a proximity of the RFID tag reader when placedat a detection point of the event, identifying a tag read time of thereceived RFID tag read, and a data interface for transmitting the RFIDtag number and the identified RFID tag read time, an image capturesystem with an image capture device and a data interface configured forreceiving an instruction for capturing an image of the participantassociated with the RFID tag number, receiving an indication that theRFID tag reader has received the RFID tag read of the RFID tag number ofthe participant, and capturing at least one image of the participantwhen the RFID tag of the participant is in proximity to the RFID tagreader responsive to the received indication, generating an imagecapture message including the image, and transmitting the image capturemessage over the data interface, and a timing system having a processor,a data communication interface, a memory and computer executableinstructions, the timing system configured for receiving the RFID tagnumber and the RFID tag read time from the RFID tag reader, andreceiving the image capture message from the image capture system, thetiming system configured for determining a time of passing of thedetection point of the participant responsive to the received RFID tagnumber and RFID tag read time, storing the determined time of passingand the image of the image capture message in the memory, the timingsystem also configured for receiving the participant data, the assignedparticipant event number, and the preorder request from the PEMS,thereafter associating the participant event number with the RFID tagnumber and generating the instruction for capturing the image of theparticipant.

In another embodiment, an automated system provides for managing aparticipant's participation in a timed event wherein the participant istracked using an RFID tag having a unique RFID tag number, the systemincluding a participant event management system (PEMS) including a userinterface configured for receiving an input from the participantincluding participant data and a registration of the participant in thetimed event, the PEMS assigning the participant a participant eventnumber responsive thereto, the PEMS also configured for receiving apreorder request for tracking of the participant during the event, thePEMS having a communication interface configured for transmitting atleast a portion of the received participant data, the assignedparticipant event number and the preorder request, an RFID tag readerhaving a processor, a memory, a clock, an RFID transceiver receiving theRFID tag number from the RFID tag when the RFID tag comes within aproximity of the RFID tag reader when placed at a detection point of theevent, identifying a tag read time of the received RFID tag read, and adata interface for transmitting the RFID tag number and the identifiedRFID tag read time, a location device associated with the RFID tag ofthe participant, the location device having a location data receiver forreceiving location data from a location providing source, and a wirelesscommunication interface, the location detection device receivinglocation information from the location providing source, time stampingeach received location information, and transmitting tag location dataover the wireless interface, a location detection device in at leastperiodic wireless communication with the location device for receivingthe transmitted tag location data, and transmitting the receivedlocation data to the timing system, a timing system having a processor,a data communication interface, a memory and computer executableinstructions, the timing system configured for receiving the RFID tagnumber and the RFID tag read time from the RFID tag reader, andreceiving the location data, the timing system configured fordetermining a time of passing of the detection point of the participantresponsive to the received RFID tag number and RFID tag read time,storing the determined time of passing and the received location data inthe memory associated with the RFID tag number of the participant, thetiming system also configured for receiving the participant data, theassigned participant event number, and the preorder request from thePEMS, associating the participant event number with the RFID tag numberand transmitting the received location data to an output interface.

In some embodiments, the preorder request includes a designation for thedelivery of the captured image, wherein the PEMS transmits the deliverydesignation and the timing system receiving the transmitted deliverydesignation, wherein the timing system is configured to transmit thereceived tracking data over the data communication interface responsiveto the received delivery designation.

In some embodiments, the delivery designation is selected from the groupconsisting of: a web page, a web page of the PEMS, a mobile phone, anemail address, a text message, a social network wall, and an internetaddress.

In some embodiments, the preorder request includes a designation fordelivery of the tracking data during or following the event, whereinsuch delivery designation includes one or more of the following:

a) updating the participant's social network wall with the trackingdata,

b) updating a third parties social network wall with the tracking data,

c) transmitting an email to an email address including the trackingdata,

d) transmitting a text message to telephone number including thetracking data,

e) posting on a webpage a map showing the location or path traveled bythe participant based on the tracking data,

f) updating an application with the tracking data and/or determined timeof passing,

g) displaying on a coupled display a map using the tracking data, and

h) updating a webpage or display or data file in the PEMS with thetracking data.

This can also include displaying on the map a captured image of theparticipant.

In some embodiments, the PEMS includes a payment receipt interface forreceiving a payment by the participant in response to the participantregistering for the event and/or submitting the preorder request fortracking the participant during the event.

In some embodiments, the PEMS transmits a payment indicator reflectingsaid payment and identifying services associated with said receivedpayment, and wherein the timing system receives the payment indicatorfor the participant and stores the payment indicator and identifies theservices associated with the payment in a data file associated with theparticipant, such as the bib number, participant number, participantidentifier number such as the RFID tag number.

In some embodiments, the location device is a GPS receiver and whereinthe tracking data includes a plurality of GPS locations.

According to another embodiment, an automated method for managing aparticipant's participation in a timed event wherein the participant istracked using an RFID tag having a unique RFID tag number, the methodcomprising: a) in a participant event management system (PEMS) having auser interface: receiving an input from the participant includingparticipant data and a registration of the participant in the timedevent, assigning the participant a participant event number responsivethereto, receiving a preorder request for capturing an image of theparticipant during the event, transmitting at least a portion of thereceived participant data, the assigned participant event number and thepreorder request; b) in an RFID tag reader configured, detecting theRFID tag when in proximity to the RFID tag reader at a detection pointduring the event, receiving the RFID tag number from the RFID tag,identifying a tag read time of the received RFID tag read, andtransmitting the RFID tag number and the identified RFID tag read timeover a data interface; c) in an image capture system with an imagecapture device and a data interface configured: receiving an instructionfor capturing an image of the participant associated with the RFID tagnumber, receiving an indication that the RFID tag reader has receivedthe RFID tag read of the RFID tag number of the participant, capturingat least one image of the participant when the RFID tag of theparticipant is in proximity to the RFID tag reader responsive to thereceived indication, generating an image capture message including theimage, and transmitting the image capture message over the datainterface; and d) in a timing system having a processor, a datacommunication interface, a memory and computer executable instructions:receiving the RFID tag number and the RFID tag read time from the RFIDtag reader, receiving the image capture message from the image capturesystem, determining a time of passing of the detection point of theparticipant responsive to the received RFID tag number and RFID tag readtime, storing the determined time of passing and the image of the imagecapture message in the memory, receiving the participant data, theassigned participant event number, and the preorder request from thePEMS, associating the participant event number with the RFID tag number,and generating the instruction for capturing the image of theparticipant.

In some embodiments, the preorder request includes a designation for thedelivery of the captured image, wherein in the PEMS transmitting thedelivery designation and in the timing system receiving the transmitteddelivery designation, transmitting the received captured image over thedata communication interface responsive to the received deliverydesignation.

In some embodiments, the delivery designation is selected from the groupconsisting of: a web page, a web page of the PEMS, a mobile phone, anemail address, a text message, a social network wall, and an internetaddress.

In some embodiments, the preorder request includes a designation fordelivery of the captured image during or following the event, whereinsuch delivery designation includes one or more of the followingprocesses and such process are responsively performed by the timingsystem:

a) updating the participant's social network wall with the capturedimage and/or determined time of passing,

b) updating a third parties social network wall with the captured imageand/or determined time of passing,

c) transmitting an email to an email address including the capturedimage and/or determined time of passing,

d) transmitting a text message to telephone number including thecaptured image and/or determined time of passing,

e) posting on a webpage the captured image and/or determined time ofpassing,

f) updating an application with the captured image and/or determinedtime of passing,

g) displaying on a coupled display the captured image and/or determinedtime of passing, and

h) updating a webpage or display or data file in the PEMS with thecaptured image and/or determined time of passing.

An image of the route can be displayed such as a map, and the capturedimages of a particular participant can be displayed as the participanttraverses a particular location on the map.

In some embodiments, the PEMS receiving a payment by the participant inresponse to the participant registering for the event and/or submittingthe preorder request for capturing an image of the participant duringthe event. In some embodiments, the PEMS transmitting a paymentindicator reflecting said payment and identifying services associatedwith said received payment, and wherein in the timing system receivingthe payment indicator for the participant and storing the paymentindicator and identifying the services associated with the payment in adata file associated with the participant, such as the bib number,participant number, or the RFID tag number.

In some embodiments, the method also includes encrypting and/orcompressing the image that is transmitted and includes an indicator ofsuch encryption or compression.

In some embodiments, the PEMS receiving a preorder request for trackingof the participant during the event, in a location device associatedwith the RFID tag of the participant, receiving location data from alocation providing source, time stamping each received locationinformation, and transmitting location data over the wireless interface,and in a location detection device in at least periodic wirelesscommunication with the location device for receiving the transmitted taglocation data, and transmitting the received location data to the timingsystem, wherein in the timing system receiving the preorder request fromthe PEMS including the request for tracking of the participant andstoring the received location data for the participant in a data fileassociated with the participant.

In some embodiments, the PEMS receiving in the preorder request adesignation for the delivery of the tracking data during or followingthe event, transmits the tracking delivery designation in the preorderrequest and in the timing system receiving the transmitted trackingdelivery designation and transmitting the received tracking data overthe data communication interface responsive to the received trackingdelivery designation.

In some embodiments, the tracking delivery designation is selected fromthe group consisting of: a web page, a web page of the PEMS, a mobilephone, a wall of a social network, and an internet address.

In some embodiments, the preorder request includes a designation fordelivery of the tracking data of the participant during or following theevent, wherein such tracking delivery designation and the processes ofthe timing system include one or more of the following:

a) updating the participant's social network wall with the tracking dataand/or determined time of passing,

b) updating a third parties social network wall with the tracking dataand/or determined time of passing,

c) posting on a webpage the tracking data and/or determined time ofpassing,

d) updating an application with the tracking data and/or determined timeof passing,

e) displaying on a coupled display a map showing the location based onthe tracking data for the participant, and

f) updating a webpage or display or data file in the PEMS with thecaptured image and/or determined time of passing.

In some embodiments, the PEMS system hosts a webpage including the userinterface.

In another exemplary embodiment, an automated method for managing aparticipant's participation in a timed event wherein the participant istracked using an RFID tag having a unique RFID tag number, the methodcomprising: a) in a participant event management system (PEMS) includinga user interface: receiving an input from the participant includingparticipant data and a registration of the participant in the timedevent, assigning the participant a participant event number responsivethereto, receiving a preorder request for tracking of the participantduring the event, transmitting at least a portion of the receivedparticipant data, the assigned participant event number and the preorderrequest; b) in an RFID tag reader having a processor, a memory, a clock,an RFID transceiver: receiving the RFID tag number from the RFID tagwhen the RFID tag comes within a proximity of the RFID tag reader whenplaced at a detection point of the event, identifying a tag read time ofthe received RFID tag read, transmitting the RFID tag number and theidentified RFID tag read time; c) in a location device associated withthe RFID tag of the participant: receiving location data from a locationproviding source, time stamping each received location information, andtransmitting tag location data over the wireless interface; d) in alocation detection device in at least periodic wireless communicationwith the location device: receiving the transmitted tag location data,and transmitting the received location data to the timing system; e) ina timing system having a processor, a data communication interface, amemory and computer executable instructions: receiving the RFID tagnumber and the RFID tag read time from the RFID tag reader, receivingthe location data, determining a time of passing of the detection pointof the participant responsive to the received RFID tag number and RFIDtag read time, storing the determined time of passing and the receivedlocation data in the memory associated with the RFID tag number of theparticipant, receiving the participant data, the assigned participantevent number, and the preorder request from the PEMS, associating theparticipant event number with the RFID tag number, and transmitting thereceived location data to an output interface.

In some embodiments, the PEMS receiving in the preorder request adesignation for the delivery of the captured image, and in the timingsystem receiving the transmitted delivery designation in the preorderrequest and transmitting the received tracking data over the datacommunication interface responsive to the received delivery designation.

In some embodiments, the delivery designation is selected from the groupconsisting of: a web page, a web page of the PEMS, a mobile phone, anemail address, a text message, a social network wall, and an internetaddress.

In some embodiments, the preorder request includes a designation fordelivery of the tracking data during or following the event, whereinsuch delivery designation includes and the timing system responsivelyperforms and/or initiates one or more of the following:

a) updating the participant's social network wall with the trackingdata,

b) updating a third parties social network wall with the tracking data,

c) transmitting an email to an email address including the trackingdata,

d) transmitting a text message to telephone number including thetracking data,

e) posting on a webpage a map showing the location or path traveled bythe participant based on the tracking data,

f) updating an application with the tracking data and/or determined timeof passing,

g) displaying on a coupled display a map using the tracking data, and

h) updating a webpage or display or data file in the PEMS with thetracking data.

In some embodiments, the PEMS includes a payment receipt interface forreceiving a payment by the participant in response to the participantregistering for the event and/or submitting the preorder request fortracking the participant during the event.

In some embodiments, the PEMS transmits a payment indicator reflectingsaid payment and identifying services associated with said receivedpayment, and wherein the timing system receives the payment indicatorfor the participant and stores the payment indicator and identifies theservices associated with the payment in a data file associated with theparticipant, such as the bib number, participant number, or the RFID tagnumber.

FIG. 1 is a schematic illustration of a typical integrated timing systemSTS system configuration that is used to read detect the passing of aparticipant P by a detection or monitored point MP during an event alongroute R at a velocity V_(A). In this exemplary embodiment, a Race BibTag T_(A) passes detection systems DS₁ that can be RFID detectionsensors DS₁ that are mounted overhead and on the side of an eventcourse. The specific location of the detection sensors DS can be changedto include any position that is deemed suitable for receiving the BibTag signal from the tag T_(A) according to one exemplary embodiment. Thedetection sensors DS (shown as DS_(N) such as DS₁, DS₂, DS₃ typicallyinclude at least a locally mounted antenna and possibly additionalsupporting electronics. As shown in an exemplary embodiment of FIG. 1, atypical Timing System TS for detecting and timing of a participant orobject passing a detection point MP by reading an identification tagT_(A) placed on the participant P or object (generally referred fromhereon as a participant, but meaning both a participant of an object)such as an RFID a Race Bib Tag T_(A) of a participant P as theparticipant P travels along route R and passes detection sensors DS₁such as RFID detector antenna that are mounted overhead and on the sideof a race course proximate to the monitored point MP. In someembodiments the DS sensors are mounted under a mat or in or on abollard. The specific location of the detection sensors DS₁ could bechanged to include any position that is deemed suitable for receivingthe Bib Tag signal from the tag T_(A) according to one exemplaryembodiment.

FIG. 2 illustrates another RFID TS 200 has two spaced apart RFID tagreading systems TRS_(F) and 114 TRS_(F+1) 114 each having a plurality ofdetection systems DS₁ and DS₂ respectively that can include wirelessantenna at a different spaced apart monitored point. The timing systemTS 116 is coupled to the PEMS 117. In this application, TRS_(F) monitorswith detection sensors DS₁ at monitored point MP_(F), which is alsoshown here as Reference point F REF_(F). TRS_(F+1) monitors with RFIDdetection sensors DS₂ at monitored point MP_(F+1), that is space at adistance of D_(F+1) behind MP_(F). The PEMS 117 is shown as well as thevarious outputs for PEMS designated delivery of tracking data or images.The RFID TS 200 can read tag T_(A) at various detection points DP alongthe participants route VA, such as DP₁ and then DP₂ as the participant Papproaches monitored point MP_(F). An addition read can be taken at themonitored point MP as DP₃. Each of these and the tag reads can be takenby either TRS_(F) or TRS_(F+1), however, in some embodiments, the RF canbe adjusted and the system software can be written so that tag reads ofDP₁, DP₂ and DP₃ are read or at least the tag reads sent, are only thoseas read by detection systems DS₁. As the participant continues pastmonitored point MP, TRS_(F+1) and detection sensors DS₂ can read the tagT_(A) at additional detection points DP₄ and DP₅ by way of example. DP₅is shown to coincide with monitored point MP_(F+1), but additionalmonitored points can be utilized and they can be at other positions.

FIG. 3 illustrates a timing system architecture having an integratedtiming system 300 that includes participant detection using RFID tagreads, laser detection and/or location determination for triggering thecapturing and associating a photograph or video with a participantaccording to various exemplary embodiments. As shown in FIG. 3, in oneembodiment a TS 116 has an image/video interface for receiving capturedimages through integration of image capture devices (ICDs) that arecontrolled by an Image Controller or Image Control System (IC) 130 forintegrating with the timing system TS 116. The interface on a TS 116 canbe wired, wireless, USB, Ethernet, by way of example. A timing system TS116 can support multiple still or video image capture devices ICDs suchas cameras connected via various interfaces. For example, in oneembodiment, a single TS 116 can received between 4 and 12 image inputsdirectly and can support higher numbers such as 200 to 300 (such as 255)ICD cameras connected through remote TS devices using an TSinterconnecting protocol. A remote device could be another TS system ata different timing/detection point such as at a different point along aracetrack or an assembly line. For example, a race or assembly line mayhave 5 timing points/detection points along the course or assembly line.One or more ICDs for videos or photos can be placed at one or more orall of each timing point and all such images can be sent back a singleTS system 116 such as one at a finish line or main TS system fordisplaying on image displays or for transferring via a protocol to awebpage 314 and 322, mobile device 316, 320, sent to a KIOSK 310 orbroadcast network 324, sent via a SMS text message 318 or email 312.These various captured image outputs 304 are managed by PEMS Push Server302 or a module within the timing system 116 or related system. If anevent such as a race, the race operator can display an image of aparticular participant on a KIOSK 310 so that the participant orinterested parties can see images of the participant passing aparticular detection point MP, such as the finish line, on a TSannouncement display, Kiosk 310, webpage 314, social network wall 322,or mobile device 316 such as a tablet 320, after the participantfinishes the race. This can also be updated a wall on a social networkwall 322 automatically as instructed or preorder by the participant or athird party. The IC 130 can capture single images as well as videostreams and it synchronizes the capture images to the RFID tag read.

To provide additional interoperability, the system 300 can include animage encryption/compression system 306 or application that canencryption and/or compress the captured images and/or convert the formatto a format as required by a selected or desired output 304.

Also shown is the integration with the laser detection system LDS 120that utilizes the laser detectors 122 for detecting the proximity of aparticipant at a monitored point MP as also shown in FIGS. 6 and 7. Inthese embodiments, the LDS 120 can be used to identify the proximity orpassing of the participant P for triggering a capturing of an image orimages. Further, as shown in FIG. 3, a location detection system LoDs124 can provide the timing system TS 114 with a geographic location of aparticipant P through receiving a location from a location determinationsystem LoD 126, such as the GPS system or a mobile device or mobiletelephone network, by way of example.

When a participant identifier or tag T_(A) tag is read, an image is alsocaptured and the two are identified with a common participant numbersuch as a RFID Chip or Tag. In other words, the TS 116 database has afield that contains a unique identifier that is typically associatedwith a participant such as a bib or contestant number. The RFID chipreads and any images or video are all commonly associated and in someembodiments, the image is associated with the RFID tag number of theassociated RFID chip read.

The image or video file itself has a file name that contains a uniquenumeric entry that identified the image. For example, if a race occurson Jan. 20, 2011 at 11:05:23.014 am in St. Louis, Mo. and theparticipant identification number (referred herein generally as a bibnumber) is No. 25, and the number 25 is read by a detection system at astart line, a photo can be captured of participant No. 25 P25 and the“captured image file name” (CIFN) for the image would be“photocap-012011-1105014-001-XX-STL.” The first part of this file namerepresents the type of file . . . in this case a captured photo(photocap). In other embodiments, this could be a “videocap” for acaptured video or other type. The next 6 digits of the CIFN are themonth, day, and year in 2 digit representations. The next set of digitsof the CIFN are HH:MM:SS.MMM with the MMM representing milliseconds, for1,000th of a second timing accuracy, which is the time of the capture orcould be the time of the RFID tag read. As shown in this example, theCIFN does not include colons such uses “-” as a delimiter. Of courseother delimiters are also possible.

The next entry in the CIFN is for the camera position or cameraidentifier to uniquely identify which image capture device captured theimage or video. This is shown as a 3-digit field and in one embodimentcan include entries from 000 to 255, or more, or could be for more orless digits.

The next two digits of the CIFN are an indicator for the type ofencoding and compression the file is using. Here this is shown as a2-digit value that can represent up to 99 types of compression orencoding schemes, but other indicators are possible. The final CIFNentry is a variable length string that may contain any identifier forthe event/race assigned by the user or STS operator. In this example,the identifier is STL reflecting that it was a St. Louis event.

In addition to static capture of photos and streaming video, the hereindescribe how the TS 116 with the integrated imaging capability enablesan event operator, participants, or third parties such as the media oradvertisers to such events to subscribe to image/video events and toreceive photos or image streams in real time or subsequently. Thedescribed TS architecture makes it possible to provide live video feedsto anyone who has need for them. For example, if an event such as a racewas being broadcast by a sports television channel, the broadcastcompany could receive photos or streaming video from the event.

In one exemplary embodiment, a plurality of image capture devices forcapturing single images or video (generally referred herein simply as animage) with each being associated with a different detection point.

The image capture devices are integrated with the participant detectionsystems (DS) of a timing system TS so that an image is captured incoordination with a detection by a detections system (DS) at itsdetection point. The DS can be an RFID tag reader, laser detectionsystem (LDS), or any other system that can detect the presence of aparticipant or object within the view of the image capture device (ICD),and can include, in some embodiments, the ICD itself.

The captured image is tagged and transmitted to a STS and stored, or atleast a link/address/pointer is stored with the detection info or userinfo. I would assume that each stored image file can also be tagged aswell as the user file including the pointer, at least as an option. Theimage can be stored with a file name that identifies it such thatsomeone could see a list of file names and know which file (image) theywanted to review. also store a pointer within the user database recordthat points to the file image. This allows the user to pull up theresults for a race participant and also view the images for that person.

The PEMS functionality is shown as 117, wherein some or all of a portionof PEMS 117 can be performed by the PEMS itself or by the TS.

FIG. 4 illustrates one exemplary on course layout of an event coursehaving image capture devices located behind an RFID tag reader TRS 114monitored point MP₁. In this illustration, the participant P is detectedby the RFID tag reader detectors DS₁ at detection point DP₁ and thenlater at detection point DP₂. The TRS 116 or detection system DRS₁ 114detects the participant's identifier such as an RFID tag number tag fromtag T_(A) and sends an image capture signal to the Image Control System(IC) 130 that controls the image capture device ICD located at imagecapture point ICP. As shown, a first image capture IC1 is taken afterthe participant is detected by DS₁ and TRS 116 at DP₁. A second imagecapture IC₂ is taken after the TRS 114 and DS₁ detect the RFID tag atDP2. The IC 130 transmits the captured images IC₁ and IC₂ back to theTRS 116 and/or the TS 114 wherein the images IC₁ and IC₂ are associatedwith the RFID tag numbers of the RFID tag reads or the other participantidentifier numbers as may be applicable. As also shown, the locationdetection system 124 can detect a location of the participant such asGIS location data form a GPS device located on the participant P such asa mobile tracking tag T_(A) or a mobile smart phone. The locationdetection system 124 is coupled to the TRS 114 and/or the timing system116 for providing the participant location data thereto. The PEMS 117provides the participant data including the participant number from theregistration as well as an image capture request and information relatedto the desired image capture delivery or output location and format.FIG. 3 also illustrates the integrated clock 204 or timing systems forboth the image capture controller 130 as well as the TRS 114 and/ortiming system 116.

FIG. 5 illustrates a similar layout as FIG. 4, but having a plurality ofimage capture devices ICD₁ taking IC₁, ICD₂ taking IC₂, ICD₃ taking IC₃,ICD₄ taking IC₄, ICD₅ taking IC₅, ICD₆ taking IC₆, and ICD_(A) takingIC⁷. Also shown are a plurality of runners Pa and Pb, with each having aplurality of RFID tag reader or detection system detection pointsDP_(AN) and DP_(BN). In this exemplary embodiment, image capture deviceICD₁ can be triggered by the participant P_(A) being detected atDP_(A1), then DP_(A2) and on to DP_(A3) and DP_(A4). This progressionsupports not only the unique identification of participant A from theother participants, but also enables multiple images to be captured orfor video of the participant to be captured. As shown, the distance offirst detection can be d_(DP1) and/or d_(DP2), which can be as far asdesigned or technically capable. For instance, in some RFID detectionsystems this could 75 feet. Multiple images ICD₁, ICD₂, ICD₃, ICD₄,ICD5, ICD₆ and ICD_(A) can be taken of a single participant P_(A).Participant P_(B) can be similarly and uniquely detected by thedetection system DS₁, DS₂, DS₃ and DS₄ and or location detection system124 and where the participants number matches an image request, imagecapture devices ICD₂, ICD₄, and ICD_(A) can capture various images IC₂,IC₄ and IC₇ at detection points DP_(B1), DP_(B2), DP_(B3) and DP_(B4) asthe participant P_(B) travels the route parallel with participant P_(A).

FIGS. 6 and 7 provide two additional TS layouts each having a differentarchitecture for image capture, but both using, in part, a laserdetection system 120 for aiding in the triggering of the image capture,in addition to the RFID tag reads and the TRS 114 or TS 116identification of the RFID tag numbers associated with each RFID tag andparticipant. Also, as shown in these figures, an alternative oradditional location detection system 124 can provide a locationdetermination LOD_(PA) of each participant P. The location LOD_(PA) ofparticipant can be provided the timing system 116 for management of theimage capturing as well as other features and services as describedherein.

Referring now to FIG. 8, is a block diagram flow chart illustrating aprocess for participant preordering system PEMS that can be included asa part or all of the PEMS. As shown, in block PEMS, one or more requestsare received for preordering of images either still or video. Therequest can include the identification of the participant for whichimages are to be taken, the number of images, the selection of thelocation for the images to be taken, and the desired delivery system ormethod for such image delivery. The delivery can be requested as beingduring an event or following an event. The delivery sites or locationsare shown, by way of example, in FIG. 3 to include a local Kiosk, awebsite, a cell phone, a tablet, or could include a broadcast channelsuch as a network broadcast station. The PEMS 117 provides the requestto the TS 116 for the planned capturing, processing and delivery of thepreorder images of the particular participant by participant identifiernumber such as an RFID tag number as provided in the request from thePEMS 117. The TS 116 can provide this information to the RFID tag reader114 as well as the image capture controller 130 in some embodiments. TheTS 116 is coupled to the TRS 114 for receiving detections or tag readsand receiving a detection of the participant in proximity thereto.

The TS 116 identifies the detected participant having preordered animage capture and send an instruction to the image capture system 130and or the image capture devices ICD. The timing system can also providethis information to the TRS 116 that in turn provides the instructionfor image capture upon detection directly to the image capture system130. The TRS 114 receives an RFID tag detection that is the RFID tagnumber of the request and can trigger the capturing of the image of theparticular participant by one or more ICDs. In alternative or additionalembodiment, the laser detection system 120 detects the passing by amonitored point and can trigger the capture of an image of theparticipant detected thereby. In other embodiments, the locationdetection system 124 can provide the location of the participant P tothe timing system 116, the TRS 114 and/or the ICS 130 for triggering thecapturing of the image based on a determination by such system that theparticipant is passing a point or location for which an image capture isdesired or is consistent with the image request. Once the ICD takes therequested image or video of the particular pre-identified participantbased on the identification by the TRS 1114, the captured images and theTRS tag reads with the RFID tag numbers can be stored in memory 706locally or provided to the TS 116 where they are stored in memory 706such as by their participant identifier numbers such as RFID tag or bibnumbers. Subsequently, the TS 114 can transmit the stored image data toan imaging system IS 119 or to the PEMS 117 or directly or indirectly tooutputs 304, such as, by way of example, the participant's social webpage or wall 322.

FIG. 9 illustrates one exemplary embodiment of a user interface for PEMS117 for receiving manual data entries from a user according to oneexemplary embodiment. As shown in FIG. 9, the PEMS 117 can include auser interface 154. The user interface 154 can include a user screen 155can include be a text box 156 on the left side of the screen 155. Theparticipant can enter his name in 158 or identifier such as a bib numberfrom a prior race in 155. As the user types in his name or number andother user data, the PEMS system registers the participant and assignsthe participant a participant identifier number. Display area 176prompts the user or provides the user with instructions of furtherinformation on possible selections. The PEMS 117 can also receive aninput from the participant either at the time of registration or at anysubsequent time prior to and during the event, for various services oroptions via selection of predefined buttons, 160, 162, 164, 168, 170,172, and 174. These can include the selection of particular optionalpackages offered for the event including image captures and the types ofimage capture and formats. the participant can be directed to input into158 their output addresses or information and as payment for anyoptional services. The user screen 155 can be adapted for webpagebrowsers for computers, tablets, or smart phones. A logout or exitbutton can also be provided.

The PEMS 117 user interface 154 receives the request for an imagecapture from the participant or possibly a third party where allowed toby the participant. The image capture request can request the number ofimages captured, the amount of video captured, the locations for whichthe images are to be captures, as well as the desired outputs 304 suchas addresses thereof. The participant can then also be prompted to payfor such image capture requests by prompting for payment via credit cardor other means. The PEMS 117 via a user interface as shown in FIG. 9 orany other suitable user interface can collect the participantinformation, establish the participant for an event, and then providesuch information along with any image capture request, paymentverification, image capture output addresses and selections and formats,to the timing system 116.

ITS Net

FIG. 10 is a high level architecture of an Integrated Timing System ITShaving timing system TS 116 each of which may have detection systems1164A and 114B that are tag reading systems 114 (shown as 114A and114B), coupled to a PEMS 117 via ITS NET communication network 118. Alsothe ITS 116 and TRS systems 114A and 114B can communicate with locationdetection system 124 or laser detection system 120 in support ofparticipant proximity detection and in support of image capture servicesand other related participant services consistent with this disclosure.Further image capture controller 130 provides the interface forcapturing the instructed images and delivering them to the ITS 116 orother specified destination.

ITS NET Cloud Architecture

FIG. 11 is a high level architecture of an Integrated Timing System ITShaving one or more timing systems TS each of which may have one or moreRFID or other automated tag reading systems 114 (shown as 114A and114B), a timing system 116 and a plurality of PEMS 117 that are theremote entry systems. The system communicate over the ITS NETcommunication network 118 and the PEMS system 117 communicates with theother ITS 116 systems over the ITS NET communications link 152. Asillustrated, multiple ITS systems 116 can be used on a communicationsnetwork 118 to send participant information to any one of several TSRFID Systems TRS 114 or to the TS 116. Each TS TRS 114 can be configuredto interface with PEMS 1117 and can be addressed individually through aconfiguration option in the PESM 117 that allows the PEMS user torequest image captures as well as to define the outputs 304. FIG. 10illustrates that each ITS 116 and TRS system 114 can communicate orinclude a location detection system 124 or laser detection system 120 insupport of participant proximity detection and in support of imagecapture services and other related participant services consistent withthis disclosure.

As shown in FIG. 11, TS_(A) 116A is implemented via communicationssystem 118 with TS_(B) 116B having two TRS_(B) systems TRS_(B1) 114B1and TRS_(B2) 114 _(B2). Next the system 200 also has TS_(C) with asingle TRS_(C) 114 _(C) system. TSD 116 _(D) has two TRS_(D1) 114 _(D1)and TRS_(D2) 114 _(D2) participant detection systems.

ITS with PEMS

FIG. 12 is schematic drawing showing the communication interfaces for anintegrated timing system ITS with a timing system TS 116 and tag readersystem (TRS) 114 configured for compatibility with a PEMS system 117according to one exemplary embodiment. A typical PEMS 117 to TS 116 andTS 116 to PEMS 117 communications architecture 250 can include aDistributed Clock System DCS 204, one or more timing systems TS 116,PEMS 117, a location detection system 124 and a laser detections system120. The PEMS can include any type of computing platform withoutlimitation.

ITS Message Protocol Structure

FIG. 13 is an illustration of the format for the variable length TS toPEMS packet message messages according to one exemplary embodiment. Asshown, FIG. 13 illustrates a variable length message information packetstructure that is used to communicate event data. This packet maycontain any type of information and the format of the packet includesthe following: message type, source, custom field(s), and end of messageindicator. Several message types are already defined, as documentedbelow. However, the message type may contain any text that uniquelyidentifies a message. The system receiving the message will use themessage type to determine the action required. The next field in thepacket includes the source. The source is a name or unique identifierthat indicates which system transmitted the message. This information isused by the receiving system to know where to send a response. Thesource field can include any text, but typically the IP address of acomputer or device is used. The next fields within the packet arecustomer fields that may contain any type of information. Theflexibility of the protocol makes it possible to send any type ofinformation from one system to another. The final field that should beincluded in each information packet contains EOM|. This is the end ofmessage indicator that is used by the receiving system to know when allinformation within a packet has been received. The packet also uses the| character to delimit each field.

METS Protocol Flow

FIG. 14 is an illustration of the formats for an exemplary set of METSmessages according to one exemplary embodiment. There is shown thepre-defined information messages provided within the protocol. Thefollowing describes each message:

(A) Read message (READ). This message can be sent from a system that hasjust read a participant tag or other participant identifier. The messagecould be sent to any other device(s) and the message includes the tagserial number just read. It also includes the time of the tag read aswell as an optional packet number. The READ message is the primaryinformation packet used to communicate tag read data to all devices. Thepacket could be expanded to include additional fields as necessary.

(B) Read message (READ). This message can be sent from a system that hasjust read a participant tag or other participant identifier. The messagecould be sent to any other device(s) and the message includes name ofthe participant that corresponds with the tag serial number just read.It also includes the time of the tag read as well as an optional packetnumber. The READ message is the primary information packet used tocommunicate tag read data to all devices. The packet could be expandedto include additional fields as necessary.

(C) Re-send message (RESEND). This message can be sent from a receivingdevice to a transmitting device to request another send of a particularpacket. If packet numbers are being used for the purpose of verifyingthat all packets are received, the re-send message can be used torequest another transmission of a packet that never arrived at thereceiving device. The packet could be expanded to include additionalfields as necessary.

(D) Time Sync (TSYNC). This message can be sent to all devices on thenetwork to indicate the current time at the transmitting device. Thismessage is used to synchronize the time on all devices, which is crucialfor RFID systems that are used for timing sporting events.

(E) Look up (LOOKUP). This message allows a device to request raceinformation from another device. The identifier may be any text. In mostcases, the identifier will be a tag serial number, race bib number,participant name, or perhaps a unique identifier that refers to aparticular type of information. For example, if a device needs to knowthe current duration of a race, the LOOKUP message could be sent to atime system that is tracking the total race time. The identifier fieldmight contain the text entry “RACETIME” and this entry could be used toindicate that the race duration is desired. The packet number field isoptional and if not used, the field could contain a single space.

(F) Command. This message could be sent to a device to request that aparticular command be executed. The IDENTIFIER field may contain anytext desired. This field could be used to send any tag reader orparticipant detection system command to a remote device. For example, ifthe current battery charge level on a remote system needed todetermined, a Command message could be sent with the text BATTERYSTATSin the IDENTIFIER field. The remote system would need to have functionsbuilt in that can process the command.

(G) RSIG. The RSIG message is sent using PEMS-TS to any system that islistening for RSIG command. This is typically used by ITS PEMS to makesure the connection over the network is good to PEMS-ITS and also toverify that PEMS-ITS is scanning and listening for PEMS entries.

(H) RQIMAGE. The RQIMAGE message is sent to a device to request that aparticular image be returned. The message is useful when interfacingwith a system that contains photographs or other pictures such as logosor artwork. The IDENTIFIER field should contain a unique descriptor forthe image desired and may contain any text desired. Typically, thisfield will contain a unique number for a participant in an event.However, the IDENTIFIER could also contain a specific location on a METSsystem where a file is located.

(I) STIMAGE. The STIMAGE message is sent from a system responding to arequest for an image, e.g., RQIMAGE. The IDENTIFIER field should containthe unique descriptor for the image that was requested and that maycontain any text desired. Typically, this field will contain a uniquenumber for a participant in an event. However, the IDENTIFIER could alsocontain a specific location on a given system where a file is located.

The STS-ICS facilitates and streamlines the communication of tag readeror participant detection system timing information between multiplecomputers used at sporting events. The protocol is flexible andadaptable and can be used to transmit any type of information across anytype of network. The use of variable length messages makes it possibleto customize the messages sent or received from any type of device. Theprotocol is simple and efficient and can be quickly implemented.

The foregoing descriptions of specific embodiments of the present designhave been presented for the purposes of illustration and description.They are not intended to be fully exhaustive or to limit the design tothe precise use, form, or methods disclosed, and it is obvious that manymodifications or variations are possible in the light of the informationprovided above. The embodiments were chosen, shown, and described inorder to best explain the concepts and principles and the practicalapplication of the design, thus providing others skilled in the art theability to best utilize the design and various embodiments with variousmodifications as are suited to the particular use desired.

TS to PEMS Output File

The TS system can be configured when equipped for PEMS to allow the userto define the output file that will be used to store METS received chipreads coming from the METS reader. The METS Remote Output File can be astandard text file that contains some basic information including thenumber of the antenna that last read the chip, the chip number, and thetime of the read. This output file can be read by Microsoft Excel, anytext editor, and virtually any database. The file is really used as abackup in case of a system failure. The output file can be used toreconstruct a database. For example, if the user has the own SQLdatabase engine and the user wish to record the chip reads in thatdatabase, the user will want to use this text file. In addition, if theuser is using a third-party race scoring system such as Race Director orRunscore, this file will be helpful to the user since both programs canread it directly. Most users can simply use the built-in database withinthe ITS. It will automatically manage the complexities of race timingand save the user a lot of effort.

Output File Merge Report

This report is a very powerful and sophisticated tool that is rarelyused for most races. However, its purpose is to provide extreme levelsof redundancy for chip timing at events in which the user want tomaximize the chip reads at a finish line.

A single TS at a typical finish line for most events should read well aslong as the chip is being worn properly and is actually on theparticipant. When a second the TS system and/or TRS used at a finishline, the combination of the two systems greatly enhances the chances ofreading the timing chips. Nonetheless, it is still possible that amissed chip read could occur. This can happen because the chip may havebeen accidentally damaged by the runner, or perhaps the chip wasaccidentally removed from the bib or other surface where it was placed.If the user has timed enough races, the user knows that strange thingshappen that are often out of the control. Nonetheless, the user may needto time a race in which it is critical that the user maximize the readsuccess. Thus, the user has an option that will improve the readsuccess.

To guarantee maximum redundancy and success at this unique race, theuser will also have an operator at the back of the finish chute that isusing a Remote Entry Software (METS) to simply enter bib numbers forevery person that has finished the race. This extra operator is simplymaking sure that every participant's race number has been keyed into thesystem. If any runner has lost their bib number, the operator can simplykey in their name as well. The result is that the user has an outputfile being created by this backup operator that contains a list of bibnumbers.

The Output File Merge Report scans the output file created by at thefinish line, looking for entries that contain a 0 for the bib number. Inother words, it finds every entry that the operator made at the finishline when they could not see a bib number and simply pressed the Enterkey. When they pressed the Enter key without a bib number, a 0 waswritten to the output file along with the time. Thus, has a finish time,but now needs to figure out who belongs with that finish time.

It now scans the Output File that came from the computer running theMETS software. The user will actually copy this file from the computeronto the hard disk of the TS at the finish line. The report now matchesup the race finishers based on numbers and times and reconciles the twooutput files. The result of this complex but quick process is that theuser will have a new output file. This file contains the combinedresults for the race with all the bib numbers of all of the participantcontained in it. The user can then load this output file into the TS asthe finish times for everyone in the race. The user could also load thisfile into a spreadsheet or any other program.

TS Database File

The TS system can include a high-speed binary database that runs inmemory and is updated very rapidly when chips are being read. When thisdatabase is saved to the disk drive, it is written to a text file usinga comma-delimited format. This allows the file to be read by third-partyprograms without having to build a complex database interface. Forexample, Microsoft Excel or Notepad can directly read the file.

The following is a sample database file record: 1,JayCooper,08:00:00,08:15:00,00:00:00,00:00:00,00:00:00,08:45:00,00:45:00,50,HalfMarathon,M,Allentown,Team Cooper,50001,Club Member,#76435,137.

The TS system can have the capability to automatically write out thedatabase during a race to a file name selected by the user.

The following is one exemplary format for the database file:Bib#,Name,StartTime,Split1,Split2,Split3,Split4,FinishTime,ElapsedTime,Age,Division,Gender,City,TeamName,ChipField,UserField1,UserField2,UniqueID.

The Bib # field will contain a value from 1 to 99999 depending on theversion of the TS system in use.

The Name will contain the full name and is typically formatted as FIRSTNAME LAST NAME with no comma between the first and last name. The usershould not include a delimiter of the TS system in this field. If the TSsystem uses a comma for example, the user should not include a comma inthe name field, of course other delimiters are also possible. When theTS system loads the database file, it uses the comma to determine theindividual fields. Thus, if the user place a comma in the Name field,the user will cause TS to use the wrong fields for the remaining entrieson the line being read.

The following fields all contain a time based on the time of day: StartTime, Split1, Split2, Split3, Split4, Finish Time. All of these fieldsare in the format HH:MM:SS and there are no quote marks.

The Age field will contain up to three digits typically ranging from oneto 100. The Division field will contain a text entry that can be up to250 characters in length, although it is typically 20 or less characterslong. The Gender field will contain a text entry that can be up to 250characters in length, although it is typically one character with eitheran M or F entry. The City field will contain a text entry that can be upto 250 characters in length, although it is typically 25 or lesscharacters long.

The Team Name field will contain a text entry that can be up to 250characters in length, although it is typically 25 or less characterslong.

The Chip field is reserved for a future update. It will contain a textentry that can be up to 250 characters in length, although it isexpected to be six or less characters long.

The UserField1 field will contain a text entry that can be up to 250characters in length, although it is typically 25 or less characterslong. This field may be used by the software to contain values relatedto team order for relay races. In some embodiments, the user will placeinformation in this field related to the user's personal informationsuch as emergency contact number.

The UserField2 field will contain a text entry that can be up to 250characters in length, although it is typically 25 or less characterslong. This is a second field that often contains additional personalinformation about a race participant.

The UniqueID field will contain a text entry that can be up to 250characters in length, although it is typically 10 or less characterslong. This field is often used to track race-day numbers or other uniquevalues that identify a race participant. TS can automatically insert aunique value in this field during the rapid registration process in thesoftware.

Not only will TS write this text file to the disk drive, it will read itback in. Thus, the user could create a database file using this formatand the TS system may read it just fine. It is important to make surethat any time fields the user creates are in the HH:MM:SS format withleading zeros on any times that are less than 10. For example, if thetime is 9:10 am, the field should contain the entry 09:10:00. In mostembodiments, if the user are creating a new file that will be loadedinto TS, the time fields should contain 00:00:00. However, if the userhas a race with assigned start times, the user could load them into TSas well by using the StartTime field.

ITS NET Protocol Messages

Generally, as described herein, an ITS compatible component or systemcan have a state-less UDP network interface that is used for outboundand inbound messages. These messages include outbound packets from TSfor READ information, as well as other data. In addition, the ITScomponent can listen for messages from other ITS systems or third-partyprograms. This interface allows third-party programs to be developedwhich can work within the ITS NET architecture.

Network and Web Settings

In order for ITS NET compatible component/system to communicate messagesfrom any ITS system or component, the ITS NET compatiblecomponent/system should have the network values set in the communicationprogram software. The ITS NET compatible component/system has a powerfulnetworking protocol that allows the user to interface to third-partyapplications, programs the user may have written, and to a number ofadd-on software programs that provide enhanced functionality. Thenetworking options allow the user to define specific locations andnetworking interfaces that will be used to provide real-time raceinformation including chips read as well as race participantinformation. These settings should not be changed unless the user has acomplete understanding of how interfaces with third-party programs.

ITS NET Compatible Component/System Sockets

As ITS NET compatible component/system is processing messages comingfrom another ITS NET compatible system, it may determine that an errorhas occurred in the message that was received. If this is the case, itwill request that TS send the message again. To do that, it needs toknow the Socket Value that the TS system is listening on for inboundmessages. In the Defaults screen of TS, there is a value set in theListen Socket box. That value should be typed in the Sender Socket boxon this ITS NET compatible component/system configuration screen.

When the TS system is communicating with other systems, it sends thatinformation to an address on the other computers. That address is calleda Socket in the networking world. The software running on anothercomputer advertises that it is listening for messages on a given Socket.It is much like the telephone system. The user has a phone number thatother people can call. In essence, the phone number is much like asocket in the TS system. If someone sends information to the socket, theuser will receive it. Thus, for the TS system to send information to aone or more ITS NET compatible component/system, the TS system componenttasked with such communication needs to know what socket that ITS NETsystem is listening on. Thus, the Remote socket is like the phone numberfor each ITS NET system.

For example, the Remote Socket for a PEMS system can be 6000. In otherwords, the PEMS system will be listening on this number for any messagessent from an ITS system component. All PEMS systems can listen on thesame Socket and thus they can all receive the same message. In otherwords, the TS user instructs any ITS system that wants to transmit amessage to a PEMS system to transmit it using the Socket 6000.Similarly, each PEMS system can also be programmed to transmit to one ormore other ITS components based on their Socket address. For example, aprimary TRS systems can have a Remote Socket address assigned such asSocket 6010, the secondary TRS system set for Socket 6020 or it can beassigned the same as the primary at Socket 6010. The TS system can havea different Socket 6200, but can also be programmed to listen to Sockets6010, 6020 and/or 6000, to monitor all traffic and communications.

However, it takes more than just a Socket value to reach an ITS systemcomponent such as a PEMS system. It also takes an IP address. Forexample, at the TS system there can be an input for identifying the IPaddress for any of the ITS system components including the PEMS system.For the PEMS system, for example, the TS system user can enter an IPaddress for the PEMS system as Remote Name/IP associated with the RemoteSocket for the PEMS system. The user needs to enter into the TS systemthe IP address where the user wants the message sent. Think of the IPaddress as a long area code in our telephone analogy. The TS systemneeds to tell what part of the country the message should go to. In thenetworking world, an IP address looks like the following: 192.168.1.100.It is usually four different numbers with a period between them. Thesenumbers define where in the world the user wish to send the message. Inmost embodiments, the user will be focused mostly on the last number,which can range from 1 to 255. This last value actually defines whichcomputing platform that is attached to a local network the user wish toreach from among the plurality of computing platforms/computers. Forexample, if the MESTS user is using a laptop is connected to the TSsystem via a Wi-Fi router, the user might be assigned number 120, andthe full IP address might be 192.168.1.120. In an exemplary embodiment,if there are more than 255 computers on a network, the previous digitmight be changed from a 1 to a 2. Thus, if one wanted to reach computernumber 350 in a company, the user might need to use an IP address of192.168.2.100 as that would be the location of the computer on thenetwork. Notice the third value was changed from a 1 to a 2. As the usershould know by now, these last two number ranges can support up to255×255 total computers . . . about 65,000 total PCs.

In most embodiments, the ITS system related network will have less than250 computers, so most of the present embodiments are concerned with thelast digit in the IP address. If the TS system user wants to only sendmessages to one ITS system component such as a PEMS, the user can placethe IP address for that PEMS system computer in the Remote Name/IPfield. However, the address for the PC could change every time it ispowered up, if so set the last digit to 255 and the message will be sentto all PCs on the network. The value of 255 is special in networking andit means to send the message to everyone, thus anyone on the network of192.168.1.XXX will receive the message. That works just fine because theTS system is also using the Socket value to make sure that a receivingPC knows that the message is also for them. The Remote Socket and theRemote Name/IP work together to tell how to communicate with othersystems.

The TS system can be configured to include define each ITS and/or PEMSlocation by entering each particular IP address that contains the namethe ITS component such as the PEMS system associated with the IPaddress. This can be used by the TS system or other components thereofto provide additional information related to a received chip read. Forexample, this can be used to identify that the chip read was receivedfrom a particular PEMS system, versus another PEMS system or versus aTRS RFID tag reader at the primary or secondary points. For example, ifthe user is using at a split point on the course called Split 1, theuser can send the chip reads over the network to the primary system atthe finish line and the user may wish to have them stored in the Split 1column. Thus, the user could use the My Location entry to Split 1. Ifthe user is using to send chip reads to another ITS component, the usercan place the word Finish in this column and it can be used by thatsystem, such as for a display or otherwise

This explanation also applies to the Listen for Messages Enabled box.The user will simply check the box and tell it can receive messages fromother systems.

As addressed above, each ITS system can be programmed to listen to oneor more Sockets on the communication network. The listen socketinstructs the TS system component such as the PEMS system to listen formessages on that socket value. These messages may include chip reads orother types of data as will be discussed in more detail below.

The Listen Socket value is the network number that PEMS will use tolisten for messages. In the networking world, there are unique addressesmuch like a street address for the home. In order for software programsto reach another program over the network, it needs to know the addressof the destination. The number of addresses in a network can be quitelarge, but PEMS will restrict the number range to a value from 5,000 to9,999. This would allow the user to have up to 5,000 PEMS systemsrunning at the same time. In one embodiment, PEMS comes pre-set when theuser purchases the TS system to a value of 6000, but the user can changethat at any time. In this exemplary embodiment the value 6002 is usedsince by design choice the TS system defaults are set to this value atthe factory to send information to any program listening on 6002. Asknown to those of skill in the art, the user could change these valuesto any number from 5,000 to 9,999. When the user enter the value, someembodiments should not include commas as the TS system as a common canbe used by the TS system as a delimiter. Simply enter the value, such as6000. The value the user use for the Listener Socket should match thevalue set in the TS defaults for Remote Socket. For example, in oneembodiment an TS system can have a default value for Remote Socket setto 6000. The user would set the Listener Socket in PEMS to 6000.

As a quick summary of the Listen and Sender socket settings for PEMS:

-   -   1. The Listener Socket value in PEMS should match the Remote        Socket value in the TS Defaults screen.    -   2. The Sender Socket value in PEMS should match the Listen        Socket value in the TS Defaults screen.

Once the user has confirmed these settings, the user can next make surethe IP Address is set properly for the PEMS software.

ITS NET—PEMS IP Address

In the last couple of sections, the address for the networkcommunications was discussed. Not only do software programs listen orsend information using socket numbers, they need to know which computeris going to receive their messages. It turns out that a single computercould actually have two or more programs running at the same time, whichare listening for messages on different sockets. The address mentionedearlier is actually specific to a software program, and not necessarilythe computer where the software program is loaded. So, not only does theITS system need to use a socket number (address for the softwareprogram), the ITS system also needs to use an IP address.

The IP Address value should be set to the IP address of the primary TSat the finish line. The user can determine that address by using theSystem Info option in the Help Menu of TS. PEMS needs to know thisspecific address so it can communicate over the network with the ITS.Recall that it was previously mentioned that if PEMS receives a messagethat is incorrect, it would request that TS re-send that message. Thus,PEMS needs to know the IP address for the computer running the TSsoftware.

In the networking world, IP addresses are usually formatted to looksomething like 192.168.100.105. There are four numbers ranging in valuefrom 1 to 255 and they are separated by periods. This number is thecomputer's unique network address in the world!

If the system user wants to run the PEMS software on the same computeras TS, the user could enter the phrase localhost in the IP Address box.This word, localhost, is a special way of telling the PEMS software thatthe TS system is running on the same computer. The user can also set theIP Address in the TS Defaults to localhost for this to work.

This concept of using localhost can be very helpful if the user is usinga single computer for training or for doing a demonstration.

Another advanced use of the IP address has to do with Broadcasts. In thenetworking world, the user can tell a software program to send out amessage to all computers on the same network. To do this, the usersimply set the last value in the IP address to 255. The value of 255 isreserved and designated to be used for messages that should be sent toeveryone.

Here a network IP address is set to 192.168.100.255. The last value isset to 255, so messages will be sent to any computer on the 192.168.100network. That means that computers that are designated as 0.1 to 0.254will receive messages sent. For example, 192.168.100.50 would receivemessages. 192.168.100.165 would also receive our messages. Because thesetwo computers have ending addresses that are within the range of 1 to254, they will receive our broadcast message that is being sent with anaddress of 255.

If a computer had an IP address of 192.168.120.40, the system would notreceive the messages from the TS system. The user sees, although thelast value in the address is 40, the value just to the left of that is120, which indicates the computer is on a different network. In summary,the first 3 values in the IP address identify the actual networklocation, and the 4^(th) value designates the computer that happens tobe on that network. The user may want to set the IP address in PEMS tohave a 4^(th) value of 255 when the user has written his own software tocommunicate with PEMS.

Exemplary TS-PEMS Messaging Packet Structure

UDP packets are ideal for use with the TS to PEMS network interface asthey are quick and relatively easy to implement. However, there arewell-known limitations for UDP packets, and the user should becompletely familiar with these limitations before the user attempt towrite software that interfaces with the ITS system.

The following includes the packet structure for an exemplary PEMSsupported UDP packets. The TS and PEMS configured as an ITS componentcan be configured to listen and send on any socket ranging from 5000 to9999. In addition, TS can be set to send to a specific computer by usingeither the computer name or its IP address. Furthermore, TS can send toall computers on the network by using 0.255 as the last bytes in the IPaddress. For example, if the user set TS system to 192.168.1.255, itwill send its messages as Broadcast packets. All ITS message are sent asclear text contained within the UDP packet, with fields separated by |characters. |EOM| should come at the end of each message.

TS can have a state-less network interface such as provided by a userdata protocol (UDP) system as used for outbound and inbound messagingover a suitable communication network. The PEMS-TS system utilizes thesemessages to include outbound packets using PEMS-TS for READ and ANNOUNCEinformation, as well as other data as described herein. In addition, anTS using PEMS-TS monitors the Internet connection for UDP PEMS messagesfrom other PEMS configured TS system components or third-party programscoupled to the same communication network. This interface allowsthird-party programs to be developed which can work within the ITSarchitecture.

UDP packets as used by the present PEMS system can provide a very quickand relatively easy system to implement and from which to build flexibleand robust applications. While there are known limitations for UDPpackets, the describes application of the UDP packets in the PEMS systemrecognizes these limitations and adjusts the design and applicationsaccordingly whereby UDP provides a very suitable solution forcommunicating between multiple ITS systems as well as sport timingauxiliary systems (STAS) in which auxiliary applications can providevertical applications utilizing the information available within thePEMS system.

The following includes the packet structure for PEMS supported UDPmessage packets. The PEMS system including the PEMS reader and any PEMSconfigured TS system component can be configured to listen and send onany socket ranging from 5000 to 9999. In addition, PEMS can be set tosend to a specific computer by using either the computer name or its IPaddress. Furthermore, PEMS can send to all computers on the network byusing 0.255 as the last bytes in the IP address. Of course in othersystems and embodiments other broadcast messaging address can also beused and still be within the scope of the present invention. In thisexample, if the PEMS system is set to 192.168.1.255, the PEMS systemsends messages as Broadcast packets. PEMS message can be sent as cleartext contained within the UDP packet, with fields separated by the “I”characters. In many embodiments, the end of message indicator |EOM|should come at the end of each message.

As noted, the PEMS network interface can be configured for statelessbroadcast communications systems, such as UDP using a broadcasting IPaddress indicator such as 255. The networking interface can howeversupport a variety of different types of messages. These can includebroadcast messages, multicast messages and unicast messages, between andamong various PEMS enabled ITS systems and components.

In some embodiments, broadcast PEMS messages can be transmitted from aPEMS system interface over the stateless broadcast communication networkwith no addressing as to the intended recipient as well as noidentification the PEMS configured ITS system component that is sendingor sent the message. As such, each of the Broadcast PEMS messages can beread by any listening PEMS component, and once received by that PEMScomponent, the receiving PEMS ITS system component does not know whichother PEMS ITS system sent the message.

In some embodiments, multicast PEMS messages can be transmitted from thePEMS interface over the stateless broadcast communication network withno addressing as to the intended recipient. However, these messagesinclude an identification of the sending ITS system component includingthe PEMS remote system, e.g., FROM identifier. The PEMS multicastmessages can be read by any PEMS configured ITS system component andonce received by that ITS system component, the receiving ITS systemcomponent knows from which of the other communicating ITS systems themessage originated. These include, by way of example, the READ, RESEND,TSYNC, and RSIG messages.

In some embodiments, Unicast PEMS messages can be transmitted from thePEMS interface over the stateless broadcast communication network withan identification of which the sending entity is (FROM identifier) aswell as an identification of the intended receiving ITS system component(DEST or Destination identifier). These unicast PEMS-TS messages areessentially point to point messaging within a stateless broadcastmessaging communication system. Only the identified destination PEMSconfigured TS system should receive these messages and they are ignoredby all other listening TS system. The receiving PEMS configured TSsystem knows that the message was intended for its use and it knows theidentification of the sending PEMS component. These include, by way ofexample, the RESEND, LOOKUP, COMMAND, RQIMAGE, and STIMAGE messages byway of example.

It should be understood to those skilled in the art that otherbroadcast, multicast and/or unicast messages can also be developed as anapplication may require or benefit from the present disclosure, andstill be considered within the scope of the present disclosure.

Read Message (READ):

The READ packet is sent by PEMS-TS to the network and can be captured byany device that is listening on the network for UDP packets. The packetis a real-time feed of any reads that are occurring at the particular TStiming system.

Packet length=variable size

Total fields=6

READ|FROM|BIB#|TIME|PACKET #|EOM|

Packet number is a value that begins with 1 and goes to 999. Once itreaches 999, it starts over again at 1. This packet number is used toreference past messages in case a message is lost on the network and are-send is requested. Additionally a separate READ message can be usedthat includes the PARTICIPANTNAME field in lieu of the BIB#.

“PEMS” READ Message. In some embodiments of the above READ message canbe used by PEMS to the manually entered tag serial number that wasmanually entered by the user of the PEMS remote. The time entry can beautomatically generated by the PEMS remote, as described herein, or canalso be a time that is manually entered. The PEMS READ message cancontains the fields identified above, but will be described here formore detail as an example of the detail of one exemplary embodiment ofPEMS.

Generally the multiple fields that can be any length. Each field isseparated by the | character, and the last field should contain the EOM|indicator. The following describes each field:

READ—This is the type indicator and it will contain the text READ.

FROM—This is the IP address or network name for the Backup system.

TAGSERIALNUMBER—This is the tag serial number that was manually enteredinto the Backup system.

TIME—This field contains the time when the manual entry was made.

PACKET #—The Backup system can include a sequential packet number, whichallows the receiving system to know if any messages were lost during thecommunications process.

EOM—This is the last field of the READ message and it indicates the endof the message.

As a second exemplary embodiment of a PEMS READ Message, the PEMS remotecan provide for the transmission of the system and participant's namethat was manually entered, as well as the time for that entry whethermanually entered, automatically time-stamped or adjusted by the offsetfor the PEMS remote that is applicable at that time. The messagecontains multiple fields that can be any length. Each field is separatedby the | character, and the last field should contain the EOM|indicator. The READ, FROM, TIME, PACKET # and EOM are described asabove, however, in this embodiment, the field PARTICIPANTNAME is thename that was manually entered into the Backup system. This field couldalso contain any other key identifier as long as the receiving system isaware of the identifier.

Resend Message (RESEND):

The RESEND message is sent to any TS system requesting that it re-send apast message. If a message is lost over the network, a request to resendcan be made for any of the last 999 messages sent previously. PEMS-TSmaintains a buffer with the past 999 messages. Once the 999 position isused, PEMS-TS starts over at position 1. Thus, PEMS-TS system ismaintaining a circular buffer of messages.

Packet length=variable size

Total fields=5

RESEND|FROM|DEST|PACKET #|EOM|

The Destination field is the ITS system that should respond to thisrequest. This is the same name set in the ITS system defaults for “MyName” in the networking section. If a request is made for a packetnumber that has not yet been used by PEMS-TS, a packet response startingwith the BLANK field can be received.

Time Sync Message (TSYNC):

The TSYNC message is sent using PEMS-TS to any ITS system that islistening for Time Sync commands. This is typically used by ITS and PEMSto make sure the time on the TS laptop is the same as that on the ITSsystem. There can always be a slight delay in the network transmission,and as such a 0.25 to 0.5 second delay may be added to the time receivedusing PEMS-TS to compensate for the delay.

Packet length=variable size

Total fields=4

TSYNC|FROM|TIME|EOM|

The FROM field is the name set in the ITS Defaults as My Name.

As another exemplary detailed description, the PEMS TSYNC Message can bereceived at the PEMS system remote along with other ITS systemcomponents for the purposes of synchronizing the time with any othersystem on the network. This ensures that the PEMS remote system is usingthe same time, which is often required or beneficial for RFID timingsystems used at sporting events.

The TSYNC message capability can provide any desired accuracy. In oneembodiment, it can provide a level of accuracy around 1/10th of a secondwherein the time stamp is to a one-second period for the tag reads. Inother embodiments, the system can be configured to enable 1/10th or even1/100th second time stamping on tag reads and in such embodiments, theTSYNC message enabled accuracy will become even more important. In someembodiments, when a system receives the TSYNC message, the local clocktime on the receiving system is adjusted immediately. In other words,the PC clock on the destination computer is adjusted right away.

The TSYNC message can be used for distributing a standard time to eachof the connected RFID Tag Reader Systems (TRS) systems, the PEMS remotesystems or any other ITS system component that may need to record orstamp a time, message or event. In one embodiment, the TSYNC message isa simple pushed time such that all receiving devices, such as receivingTRS systems and PEMS remote reset their internal clocks to the time asreceived or specified in the TSYNC message. Additionally, ITS componentsystem including the PEMS remote can be adapted to adjust its internalclock from the exact time specified in the TSYNC message to account fortransmission system delays or variances, as may be known or predicted.

The ITS primary or supervising system, may be a ITS user console oranother system including one of the TRS systems. The selection of thestandard time within the ITS system configuration can be selected basedon the expected accuracy of the computer clock for such device or can bebased on its physical location within the network or course. The ITSsoftware provides for an initialization of the synchronization of all orsome of the coupled TRS systems and the PEMS remotes. This can bemanually initiated by a user of such system or can be configured as apart of an automated routine or process.

In some embodiments, the TSYNC message can be re-transmitted as anautomated heartbeat message to provide for regular updating and toaccount for operational variances, as well as to provide reference timesto provide updating where communication links may not continuouslyoperate. As described herein, the Sync message can be transmitted to ITScomponents and the heartbeat message can support less expensive orcomplex systems that have clocks that less accurate and can drift one ormore seconds over a 24 hour period. This can be important forapplications wherein the total lapsed time is greater than a few hours.

Additionally, the receiving or transmitting system of the TSYNC messagecan be configured for compensation for communication system ortransmission delays. This can be a predetermined or estimatedcompensation time, based on the system uses or network capabilities avalue of 0.1 seconds to compensate for the network delay. This is basedon using common Wi-Fi routers where the message delay across such arouter using UDP datagrams is between 0.05 to 0.15 seconds. UDPdatagrams are lower priority traffic, so some routers buffer themslightly.

Remote (PEMS) Signal Message (RSIG):

The RSIG message is sent using PEMS-TS to any system that is listeningfor RSIG command. This is typically used by ITS PEMS to make sure theconnection over the network is good to PEMS-TS and also to verify thatPEMS-TS is scanning and listening for PEMS entries.

Packet length=variable size

Total fields=4

RSIG|FROM|TIME|EOM|

The FROM field is the name set in the ITS Defaults as My Name.

Time Remote (PEMS) Offset Message (TROFFSET):

The TROFFSET message is sent using PEMS-TS interface and communicationsto a PEMS system from another ITS system component. This message can beused by PEMS as a input to adjust manually entered times at the PEMSsystem so that the manually entered time is offset or adjusted based onan externally provided estimate or predetermined amount of time asdetermined by the sending ITS system component.

Packet length=variable size

Total fields=4

TROFFSET|FROM|TIME|EOM|

In this message, the time is the offset set time or the amount of timefor the PEMS system to adjust the manual entered big numbers from thePEMS terminal clock that is in synchronization due to the receiving ofthe TSYNC message. The FROM field is the name set of the ITS componentoriginating the TROFFSET message. This can in some embodiments be thename set in the ITS Defaults as My Name.

Lookup Message (LOOKUP):

The LOOKUP message allows a device to request race information fromanother device. The identifier may be any text. In most cases, theidentifier will be a tag serial number, race bib number, participantname, or perhaps a unique identifier that refers to a particular type ofinformation. For example, if an ITS systems needs to know the currentduration of a race, the LOOKUP message could be sent to an ITS systemthat is responsible for tracking the total race time. The identifierfield might contain the text entry “RACETIME” and this entry could beused to indicate that the race duration is desired. The packet numberfield is optional and if not used, the field could contain a singlespace.

Packet length=variable size

Total fields=6

LOOKUP|FROM|DEST|IDENTIFIER|PACKET #|EOM|

Command Message (COMMAND):

The COMMAND message can be sent to an ITS system to request that aparticular command be executed in that ITS system. The IDENTIFIER fieldmay contain any text desired. This field could be used to send any tagreader or participant or tag detector command to a PEMS device. Forexample, if the current battery charge level on a PEMS system needed todetermined, a Command message could be sent with the text BATTERYSTATSin the IDENTIFIER field. The PEMS system would need to have functionsbuilt in that can process the command.

Packet length=variable size

Total fields=6

COMMAND|FROM|DEST|IDENTIFIER|PACKET #|EOM|

Request Image Message (RQIMAGE):

The RQIMAGE message is sent to a device to request that a particularimage be returned. The message is useful when interfacing with a systemthat contains photographs or other pictures such as logos or artwork.The IDENTIFIER field should contain a unique descriptor for the imagedesired and may contain any text desired. Typically, this field willcontain a unique number for a participant in an event. However, theIDENTIFIER could also contain a specific location on a PEMS system wherea file is located. The COMPRESSION field may be used to specify theformat of the image to be sent. If higher performance across a networkis desired, this field might be used to indicate that High compressionis desired. The field may contain any text that is recognized by thesystem designated as DEST. The PACKETSIZE field should contain a valueindicating the maximum packet size to send at one time. Given that mostimages will contain more data than is able to be sent in a singlepacket, this field may be used to control packet size, thus tuning thenetwork performance. The PSOCKET field is used when it necessary ordesired to have multiple packet streams being sent simultaneously fromthe DEST. For example, the field could contain 7000 on one packet and7001 on a different packet to indicate that two streams are being usedsimultaneously.

Packet length=variable size

Total fields=9

RQIMAGE|FROM|DEST|IDENTIFIER|COMPRESSION|PACKETSIZE|PSOCKET|PACKET#|EOM|

Image Sent Message (STIMAGE):

The STIMAGE message is sent from a system responding to a request for animage, e.g., RQIMAGE. The IDENTIFIER field should contain the uniquedescriptor for the image that was requested and that may contain anytext desired. Typically, this field will contain a unique number for aparticipant in an event. However, the IDENTIFIER could also contain aspecific location on a given system where a file is located. TheCOMPRESSION field indicates the type of compression used on the imagewhen it was sent. If higher performance across a network is desired,this field might be used to indicate that High compression is desired.The PACKETSIZE field should contain a value indicating the length of theportion of the image just sent. Given that most images will contain moredata than can be sent in a single packet, this field will be used toindicate how many bytes have been sent. The PSOCKET field contains avalue indicating which stream the information is being sent on. This maybe used when it necessary or desired to have multiple packet streamsbeing sent simultaneously from a system. For example, this field couldbe used to send individual photos to different computers on a network atthe same time.

Packet length=variable size

Total fields=9

STIMAGE|FROM|DEST|IDENTIFIER|COMPRESSION|PACKETSIZE|PSOCKET|PACKET#|EOM|

Request Image Library Contents Message (RQIDIR):

This message could be sent to a device to request that the names of allimages available be provided for that system. The message is useful wheninterfacing with a system that contains photographs or other picturessuch as logos or artwork. The IDENTIFIER field should contain a uniquedescriptor for the type of images desired or a filter mask for the namesor locations of images. For example, the IDENTIFIER might contain thetext entry *, or it might contain a qualifier such as *.JPG is the useronly wants to receive a list of images that are in JPG format.

Packet length=variable size

Total fields=6

RQIDIR|FROM|DEST|IDENTIFIER|PACKET #|EOM|

Image Library Sent Message (STIDIR): This message can be sent to one ormore systems as a response to an RQIDIR message and it includes a listof images available. The FILELIST field will contain a list of images intext format that are available. Each image name will contain a carriagereturn line feed indicator at the end of the name. If the list has beencompletely transmitted, a final indicator at the end of the list willinclude an entry of EOL followed by a carriage return line feed. Thisindicator means there are no additional packets being sent and theentire list has been provided.

Packet length=variable size

Total fields=6

STIDIR|FROM|DEST|FILELIST|PACKET #|EOM|

Request Image Stream On Message (RQISTREAMON):

This message could be sent to a device to request that a particularimage stream be enabled for a real-time video feed. The message isuseful when interfacing with a system that contains a camera displayinglive video. The IDENTIFIER field should contain a unique descriptor forthe image stream desired and may contain any text desired. Typically,this field will contain a unique name for a camera or video interface.However, the IDENTIFIER could also contain a specific socket, URL, orother indicator that is a live video stream. The COMPRESSION field maybe used to specify the format to be used when sending the video stream.If higher performance across a network is desired, this field might beused to indicate that High compression is desired. The field may containany text that is recognized by the system designated as DEST. ThePACKETSIZE field should contain a value indicating the maximum packetsize to send at one time. Since the video stream will contain a greatamount of information, the image stream can be deconstructed into smallpackets that are sent across the network. The PSOCKET field is used whenit necessary or desired to have multiple packet streams being sentsimultaneously from the DEST. For example, the field could contain 6000on one packet and 6001 on a different packet to indicate that twostreams are being used simultaneously. The TIMEOUT field can be used toindicate how long, in seconds, the stream should be kept alive. If thisvalue is set to 0, the DEST will continue to send the stream until aRQISTREAMOFF message is received.

Packet length=variable size

Total fields=10

RQISTREAMON|FROM|DEST|IDENTIFIER|COMPRESSION|PACKETSIZE|PSOCKET|TIMEOUT|PACKET#|EOM|

Request Image Stream Off Message (RQISTREAMOFF):

This message could be sent to a device to request that a particularimage stream be disabled. The IDENTIFIER field should contain a uniquedescriptor for the stream to be disabled. The PSOCKET field can also beused to identify a particular socket, in the event that multiple streamsare being sent at the same time.

Packet length=variable size

Total fields=7

RQISTREAMOFF|FROM|DEST|IDENTIFIER|PSOCKET|PACKET#|EOM|

GPS Wakeup Message (GPSWAKE):

This message can be sent to a chip or remote system to request that acommunication session begin. This message will cause the chip or remotesystem to send back parameters for the session in the buffer passed. TheLSOCKET value can be used to identify a unique socket being used for thesession. The SETTINGS value is used to request the chip or remote systemconform to specific parameters for the session. Once a session isestablished, the caller will wait for data to show up in the buffer andprocess it accordingly. Thus, this message is ideal for setting up along-term session where data will trickle in over time, into the Bufferallocated.

Packet length=variable size

Total fields=7

GPSWAKE|FROM|DEST|LSOCKET|SETTINGS|BUFFER|EOM|

GPS Wakeup and Receive Message (GPSRWAKE):

This message can be sent to a chip or remote system to request that acommunication session begin with data being returned immediately. Thismessage will cause the chip or remote system to send back GPS locationand/or time information in the buffer passed. The LSOCKET value can beused to identify a unique socket being used for the session. TheSETTINGS value is used to request the chip or remote system conform tospecific parameters for the session. Once the initial data has beenreceived the session will remain open and wait for additional data toappear in the buffer. This command differs from the GPSWAKE messagesince the GPSWAKE does not request data. It simply waits for data toshow up. The GPSRWAKE message requests that all data be sentimmediately, thus clearing the buffer on the chip or remote system rightaway.

Packet length=variable size

Total fields=7

GPSRWAKE|FROM|DEST|LSOCKET|SETTINGS|BUFFER|EOM|

GPS Receive Message (GPSRMESS):

This message can be sent to a chip or remote system to request that alldata be transmitted immediately. This is a stateless message that doesnot require a session to first be created. Thus, it is ideal for rapidcommunications with a chip or system. The LSOCKET value can be used toidentify a unique socket being used to receive the data. The SETTINGSvalue is used to request the chip or remote system conform to specificparameters for the data transmission. BUFFER will contain the actualdata coming back to the caller.

Packet length=variable size

Total fields=7

GPSRMESS|FROM|DEST|LSOCKET|SETTINGS|BUFFER|EOM|

GPS Re-Send Message (GPSRSMESS):

This message can be sent to a chip or remote system to request that thedata previously sent, be re-transmitted again. This can be used toretrieve data that may have been lost in route to the caller. This is astateless message that does not require a session to first be created.Thus, it is ideal for rapid communications with a chip or system. TheLSOCKET value can be used to identify a unique socket being used toreceive the data. The SETTINGS value is used to request the chip orremote system conform to specific parameters for the data transmission.BUFFER will contain the actual data coming back to the caller.

Packet length=variable size

Total fields=7

GPSRSMESS|FROM|DEST|LSOCKET|SETTINGS|BUFFER|EOM|

GPS Waypoint Message (GPSWAYP):

This message can be sent to a chip or remote system to request specificdata that is based on a specific or range of waypoint values. This is astateless message that does not require a session to first be created.Thus, it is ideal for rapid communications with a chip or system. TheLSOCKET value can be used to identify a unique socket being used toreceive the data. The SETTINGS value is used to request the chip orremote system conform to specific parameters for the data transmission.BUFFER will contain the actual data coming back to the caller.

Packet length=variable size

Total fields=7

GPSWAYP|FROM|DEST|LSOCKET|SETTINGS|BUFFER|EOM|

GPS Send Message (GPSSENDS):

This message can be sent to a chip or remote system to transmit dataimmediately. This message requires you to first create a session. TheTSOCKET value can be used to identify a unique socket on the remotesystem. The SETTINGS value is used to request the chip or remote systemconform to specific parameters for the data reception. BUFFER willcontain the actual data being sent. The advantage to using the GPSSENDSmessage is that the remote system will automatically handle errorhandling for lost messages that did not arrive.

Packet length=variable size

Total fields=7

GPS SENDS|FROM|DEST|LSOCKET|SETTINGS|BUFFER|EOM|

GPS Send Message (GPSSENDC):

This message can be sent to a chip or remote system to transmit dataimmediately. This message does not require a session. The TSOCKET valuecan be used to identify a unique socket on the remote system. TheSETTINGS value is used to request the chip or remote system conform tospecific parameters for the data reception. BUFFER will contain theactual data being sent.

Packet length=variable size

Total fields=7

GPSSENDC|FROM|DEST|LSOCKET|SETTINGS|BUFFER|EOM|

GPS Close Message (GPSCLOSE):

This message can be sent to a chip or remote system to let it know thattransmissions are now over and the sockets being used are released. TheTSOCKET value can be used to identify a unique socket on the remotesystem. This message is used for sessions that are always open.

Packet length=variable size

Total fields=5

GPSCLOSE|FROM|DEST|LSOCKET|EOM|

In other embodiments, the formats of the above or other PEMS messagepacket can vary from that described above and herein and still be withinthe scope of the present disclosure.

ITS-IC Network Interface Design Guidelines

The following can provide additional insight about how to use thePEMS-TS Networking Interface.

a) UDP packets are not guaranteed to be delivered on a network, as isthe case with TCP. In some networks, routers cannot automatically sendUDP packets unless they are configured to do so. For the PEMS-TScommunication system as described herein, the router should be able tosend UDP packets, as well as a broadcast datagram.

b) In some embodiments of the PEMS-TS communication system, the ITSsystem can only process inbound messages while it is connected to thetiming system and the ITS system is Enabled and Scanning as addressedabove. In such embodiments, if message packets are sent by PEMS to aPEMS configured ITS component, such sent message packets will bediscarded unless such systems are in the Scanning mode.

c) In some embodiments, the PEMS remote and or PEMS configured ITSsystem can send and receive messages only if configured to do so in thesoftware defaults. As such, the defaults should be set properly andenabling system/software may need to be rebooted after making anychanges to ensure that the networking functions have started properly.

d) When PEMS remote or PEMS configured ITS system sends a messagepacket, it can actually send the first packet, wait about 10milliseconds, and send a second identical packet. Additionally asdiscussed this can be sent more than two times and the times between theduplicates message packets can vary based on the user and systemrequirements. This architecture can increase the odds that a packet canreach the destination IP address without having to add the overhead ofan acknowledgement message function to the PEMS protocol. For example,in a PEMS configured ITS component r application, a filter can becreated to identify and discard redundant packets. In other embodiments,the receipt, analysis and management of the redundant PEMS messages canbe managed in other manners as may be desired by the user.

e) In some embodiments, the PEMS system can be designed to have minimaloverhead and functionality. As such, in some embodiments, the PEMSsystem or PEMS configured ITS system component can be configured toignore any errors. For example, the PEMS interface or functionality canbe configured so that no error messages are sent or initiated if a PEMSmessage packet is transmitted or received in an improper format. In suchembodiments, the malformed packet can simply be discarded.

f) While the ITS system is scanning for chip reads and PEMS Readmessages, it can check the ITS network packet buffer approximately every1 to 3 seconds for new messages that have been received. The PEMSconfigured ITS components can utilize an automatic load balancing systemfor packet processing. If the ITS system determines that the chip readand PEMS read low is lighter than normal, the ITS system can beconfigured to speed up the processing of inbound TRS chip read and PEMSread messages. This improve the performance of the ITS system andincrease the number of Read message from the TRS systems and the PEMSremote.

g) When either the PEMS remote or PEMS configured ITS system componentis transmitting messages to the other ITS PEMS entities, in someembodiments, such systems cannot process inbound messages until thesending or receiving of the PEMS messages is completed.

i) In some embodiments, the ITS system components and applications,including the PEMS system and the PEMS configured ITS components use onesocket for outbound packets, and a different socket for inboundmessages. Thus, any PEMS system application should use the socketsdesignated in the PEMS-TS specification or as defined by the user asaddressed later within in this specification. herein.

PEMS-TS Interfacing Application Example

The following is pseudo code for creating a PEMS-TS UDP clientapplication. This is simply an example of the type of PEMS-TScommunication code that can be implemented using the PEMS-TS system andmethod as described herein.

int main( ) { int socketnum; struct socketnumaddress_in server_address;struct hostloc *host; char packet_data[128]; host = (struct hostloc *)gethostbyname((char *)“192.168.1.255”); server_address.sin_family =AF_INET; server_address.sin_port = htons(6002); server_address.sin_addr= *((struct in_addr *)host−>h_addr);bzero(&(server_address.sin_zero),8); while (True) { printf(“Type EXITwhen done.”); gets(packet_data); if ((strcmp(packet_data, “EXIT”) == 0)){ printf(“Program done.”); exit; } sendto(socketnum, packet_data,strlen(packet_data), 0(struct socketnumaddress*)&server_addr,sizeof(struct socketnumaddress)); } }

FIG. 15 is a block diagram of a participant event management system PEMS117 used for registration and pre-ordering of participant event relatedservices according to one exemplary embodiment. As shown, a single PEMS117 can be associated with a plurality of timing systems 116A, 116B,116C and 116D, by way of example. The communication network 118 canprovide the interfacing between the PEMS 117 with each timing system116A, 116B, 116C and 116D and with outputs 304 such as KIOSK 310. All ofthese can be distributed and implemented in any manner and in anylocation. Similarly, FIG. 16 is a second block diagram of a participantevent management system PEMS 117 used for registration and pre-orderingof participant event related services and the subsequent providing ofthose pre-ordered event related services according to one exemplaryembodiment. As shown in FIG. 16, the participant using PEMS 117 userinterface inputs their name or bib number and the information is sent tothe TS 116. The particular TS 116 can then communicate with the PEMS 117the particular image capture options and services available for aparticular event as be managed by the particular timing system 116.These can include pre-purchased products for the image capture services.The participant can also select any offered options and pay for theoptions via credit card or other suitable means. The participant canalso select the output such as KIOSK 310 or this can be directed by theevent manager. The participant can provide an email address for whichthe captured image can be sent as in 312, a website url to which the FTPphoto can be posted in 314 or the telephone number that the capturedimage or images can be sent to a mobile phone or tablet in 316. Theseare only examples of some of the variations in the PEMS 117 integrationwith the ITS 116 as disclosed herein. One skilled in the art willunderstand that various combinations of these disclosed embodiments arepossible even though not arranged herein and that equivalenttechnologies are possible and are still considered to be within thescope of the PEMS 117 ITS 116 integration disclosed.

PEMS and ITS Exemplary Computer Operating Environments

Referring to FIG. 17, an operating environment for an illustratedembodiment of the ITS, the TS, the TRS and/or PEMS as described hereincan included or be implemented in a computer system 700 with a computer702 that comprises at least one high speed central processing unit (CPU)704, in conjunction with a memory system 706 interconnected with atleast one bus structure 708, an input device 710, and an output device712. These elements are interconnected by at least one bus structure708. As addressed above, the input and output devices can include acommunication interface including an antenna interface. Any or all ofthe computer components of the ITS system including the PEMS-TS networkinterface and communications systems and methods can be any computingdevice including, but not limited to, a lap top, PDA, Cell/mobile phone,as well as potentially a dedicated device. The software can beimplemented as any “app” thereon and still be within the scope of thisdisclosure.

The illustrated CPU 704 for an PEMS-TS, tag reader or detection systemis of familiar design and includes an arithmetic logic unit (ALU) 714for performing computations, a collection of registers for temporarystorage of data and instructions, and a control unit 716 for controllingoperation of the computer system 700. Any of a variety of processors,including at least those from Digital Equipment, Sun, MIPS, Motorola,NEC, Intel, Cyrix, AMD, HP, and Nexgen, is equally preferred but notlimited thereto, for the CPU 704. This illustrated embodiment operateson an operating system designed to be portable to any of theseprocessing platforms.

The memory system 706 generally includes high-speed main memory 720 inthe form of a medium such as random access memory (RAM) and read onlymemory (ROM) semiconductor devices that are typical on a PEMS-TS, tagreader or detection system. However, the present disclosure is notlimited thereto and can also include secondary storage 722 in the formof long-term storage mediums such as floppy disks, hard disks, tape,CD-ROM, flash memory, etc., and other devices that store data usingelectrical, magnetic, and optical or other recording media. The mainmemory 720 also can include, in some embodiments, a video display memoryfor displaying images through a display device (not shown). Thoseskilled in the art will recognize that the memory system 706 cancomprise a variety of alternative components having a variety of storagecapacities.

Where applicable, an input device 710, and output device 712 can also beprovided in the PEMS-TS, tag reader or detection system. The inputdevice 710 can comprise any keyboard, mouse, physical transducer (e.g. amicrophone), and can be interconnected to the computer 702 via an inputinterface 724, such as a graphical user interface, associated with orseparate from the above described communication interface including theantenna interface for wireless communications. The output device 712 caninclude a display, a printer, a transducer (e.g. a speaker), etc., andbe interconnected to the computer 702 via an output interface 726 thatcan include the above described communication interface including theantenna interface. Some devices, such as a network adapter or a modem,can be used as input and/or output devices.

As is familiar to those skilled in the art, the computer system 700further includes an operating system and at least one applicationprogram. The operating system is the set of software that controls thecomputer system's operation and the allocation of resources. Theapplication program is the set of software that performs a task desiredby an ITS user, using computer resources made available through theoperating system. Both are typically resident in the illustrated memorysystem 706 that may be resident on the PEMS-TS, tag reader or detectionsystem.

In accordance with the practices of persons skilled in the art ofcomputer programming, the present disclosure is described below withreference to symbolic representations of operations that are performedby the computer system 700. Such operations are sometimes referred to asbeing computer-executed. It will be appreciated that the operations thatare symbolically represented include the manipulation by the CPU 704 ofelectrical signals representing data bits and the maintenance of databits at memory locations in the memory system 706, as well as otherprocessing of signals. The memory locations where data bits aremaintained are physical locations that have particular electrical,magnetic, or optical properties corresponding to the data bits. One ormore embodiments can be implemented in tangible form in a program orprograms defined by computer executable instructions that can be storedon a computer-readable medium. The computer-readable medium can be anyof the devices, or a combination of the devices, described above inconnection with the memory system 706.

When describing elements or features and/or embodiments thereof, thearticles “a”, “an”, “the”, and “said” are intended to mean that thereare one or more of the elements or features. The terms “comprising”,“including”, and “having” are intended to be inclusive and mean thatthere may be additional elements or features beyond those specificallydescribed.

Those skilled in the art will recognize that various changes can be madeto the exemplary embodiments and implementations described above withoutdeparting from the scope of the disclosure. Accordingly, all mattercontained in the above description or shown in the accompanying drawingsshould be interpreted as illustrative and not in a limiting sense.

It is further to be understood that the processes or steps describedherein are not to be construed as necessarily requiring theirperformance in the particular order discussed or illustrated. It is alsoto be understood that additional or alternative processes or steps maybe employed.

The invention claimed is:
 1. An automated system for managing a trackingand an automated real-time remote reporting thereof of a participant'sparticipation in an event using an participant identifier having aunique participant identifier number, the automated system comprising: aparticipant event management system (PEMS) including a user interfacereceiving an input from the participant including participant data and aregistration of the participant in the event, the PEMS assigning theparticipant a participant event number responsive thereto, the PEMS alsoreceiving a preorder request for tracking of the participant during theevent, the PEMS having a communication interface transmitting theassigned participant event number and the preorder request; aparticipant proximity detector having a processor, a memory, a clock, anRFID transceiver receiving the participant identifier number from theparticipant identifier when the participant identifier comes within aproximity of the participant proximity detector when placed at adetection point of the event, identifying from the clock a read time ofthe received participant identifier read, and a data interface fortransmitting the participant identifier number and the identifiedparticipant identifier read time; a location device associated with theparticipant identifier of the participant, the location device having alocation data receiver for receiving location data from a locationproviding source, and a wireless communication interface, the locationdetection device receiving location information from the locationproviding source, time stamping each received location information, andtransmitting participant location data over the wireless interface; alocation detection device in at least periodic wireless communicationwith the location device for receiving the transmitted participantlocation data, and transmitting the received location data to the timingsystem; a timing system having a data communication interface, a memoryand computer executable instructions, the timing system receiving theparticipant identifier number and the participant identifier read timefrom the participant proximity detector, and receiving the locationdata, the timing system determining a time of passing of the detectionpoint of the participant responsive to the received participantidentifier number and participant identifier read time, storing thedetermined time of passing and the received location data in the memoryassociated with the participant identifier number of the participant,receiving the transmitted assigned participant event number and thepreorder request from the PEMS, associating the participant event numberwith the participant identifier number and transmitting the receivedlocation data forming at least a part of the participant tracking datato an output interface.
 2. The automated system of claim 1 wherein thepreorder request includes a designation for the delivery of the locationdata, wherein the PEMS transmits the delivery designation and the timingsystem receiving the transmitted delivery designation, wherein thetiming system is configured to transmit the received location data overthe data communication interface responsive to the received deliverydesignation.
 3. The automated system of claim 2 wherein the deliverydesignation is selected from the group consisting of a web page URL, aweb page URL of the PEMS, a mobile phone address, an email address, atext message address, a social network wall URL; and an internetaddress.
 4. The automated system of claim 2 wherein the preorder requestincludes a designation for delivery of the tracking data during orfollowing the event, wherein such delivery designation includes one ormore of the following: a) updating the participant's social network wallwith the tracking data; b) updating a third parties social network wallwith the tracking data; c) transmitting an email to an email addressincluding the tracking data; d) transmitting a text message to telephonenumber including the tracking data; e) posting on a webpage a mapshowing the location or path traveled by the participant based on thetracking data; f) updating an application with the tracking data and/ordetermined time of passing; g) displaying on a coupled display a mapusing the tracking data; and h) updating a webpage or display or datafile in the PEMS with the tracking data.
 5. The automated system ofclaim 1 wherein the PEMS includes a payment receipt interface forreceiving a payment by the participant in response to the participantregistering for the event and/or submitting the preorder request fortracking the participant during the event.
 6. The automated system ofclaim 5 wherein the PEMS transmits a payment indicator reflecting saidpayment and identifying services associated with said received payment,and wherein the timing system receives the payment indicator for theparticipant and stores the payment indicator and identifies the servicesassociated with the payment in a data file associated with theparticipant, such as the bib number, participant number, or an RFID tagnumber.
 7. The automated system of claim 1 wherein location device is aGPS receiver and wherein the tracking data includes a plurality of GPSlocations.
 8. The automated system of claim 1 wherein the participantidentifier is an RFID tag having an RFID tag number as the participantidentifier number and the participant proximity detector is an RFID tagreader.
 9. An automated method for managing a tracking and an automatedreal-time remote reporting thereof of a participant's participation inan event using an participant identifier having a unique participantidentifier number, the automated method comprising: a) in a participantevent management system (PEMS) including a user interface: receiving aninput from the participant including participant data and a registrationof the participant in the event, assigning the participant a participantevent number responsive thereto, receiving a preorder request fortracking of the participant during the event, and transmitting theassigned participant event number and the preorder request; b) in aparticipant proximity detector having a processor, a memory, a clock, anparticipant transceiver: receiving the participant identifier numberfrom the participant identifier when the participant identifier comeswithin a proximity of the participant proximity detector when placed ata detection point of the event, identifying a read time of the receivedparticipant identifier read, transmitting the participant identifiernumber and the identified participant identifier read time; c) in alocation device associated with the participant identifier of theparticipant: receiving location data from a location-providing source,time stamping each received location information, and transmittingparticipant location data over the wireless interface; d) in a locationdetection device in at least periodic wireless communication with thelocation device: receiving the transmitted participant location data,and transmitting the received location data to the timing system; e) ina timing system having a processor, a data communication interface, amemory and computer executable instructions: receiving the participantidentifier number and the participant identifier read time from theparticipant proximity detector, receiving the location data, determininga time of passing of the detection point of the participant responsiveto the received participant identifier number and participant identifierread time, storing the determined time of passing and the receivedlocation data in the memory associated with the participant identifiernumber of the participant, receiving the assigned participant eventnumber and the preorder request from the PEMS, associating theparticipant event number with the participant identifier number, andtransmitting the received location data to an output interface.
 10. Theautomated method of claim 9 in the PEMS receiving in the preorderrequest a designation for the delivery of the location data capturedimage, and in the timing system receiving the transmitted deliverydesignation in the preorder request and transmitting the receivedtracking data over the data communication interface responsive to thereceived delivery designation.
 11. The automated method of claim 10wherein the delivery designation is selected from the group consistingof: a web page, a web page of the PEMS, a mobile phone, an emailaddress, a text message, a social network wall, and an internet address.12. The automated method of claim 10 wherein the preorder requestincludes a designation for delivery of the tracking data during orfollowing the event, wherein such delivery designation includes and thetiming system responsively performs and/or initiates one or more of thefollowing: a) updating the participant's social network wall with thetracking data, b) updating a third parties social network wall with thetracking data, c) transmitting an email to an email address includingthe tracking data, d) transmitting a text message to telephone numberincluding the tracking data, e) posting on a webpage a map showing thelocation or path traveled by the participant based on the tracking data,f) updating an application with the tracking data and/or determined timeof passing, g) displaying on a coupled display a map using the trackingdata, and h) updating a webpage or display or data file in the PEMS withthe tracking data.
 13. The automated method of claim 9 wherein the PEMSincludes a payment receipt interface for receiving a payment by theparticipant in response to the participant registering for the eventand/or submitting the preorder request for tracking the participantduring the event.
 14. The automated method of claim 13 wherein the PEMStransmits a payment indicator reflecting said payment and identifyingservices associated with said received payment, and wherein the timingsystem receives the payment indicator for the participant and stores thepayment indicator and identifies the services associated with thepayment in a data file associated with the participant, such as the bibnumber, participant number, or the participant identifier number.